Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Jenkins createRelease not using User Specified package #148

Open
paulmilbank opened this issue May 2, 2023 · 2 comments
Open

Jenkins createRelease not using User Specified package #148

paulmilbank opened this issue May 2, 2023 · 2 comments

Comments

@paulmilbank
Copy link

paulmilbank commented May 2, 2023 •
edited
Loading

Hi

I have been experimenting with replacing our octo create-release with octopusCreateRelease in our Jenkins pipelines.

I noticed that the generated code when using createRelease doesn't seem to create User Specified packages, Octopus always selects the latest pushed package.

For example:

D:/Tools/OctopusTools/*/Octo.exe create-release --server https://octopus-server `
                                                                        --apikey $($env:OCTOPUS_API_KEY) `
                                                                        --project "Opserver" `
                                                                        --enableservicemessages `
                                                                        --version $($env:VERSION) `
                                                                        --progress `
                                                                        --ignoreSslErrors `
                                                                        --ignoreexisting `
                                                                        --force `
                                                                        --deploymenttimeout 00:15:00 `
                                                                        --waitfordeployment `
                                                                        --package="StackExchange.Opserver":$($env:VERSION)

output shows

The package version for some steps was not specified. Going to try and resolve those automatically...
Finding latest package for step: Add opserver to AD group
Selected 'Powershell.Infrastructure.Deployment' version '1.1.109' for 'Add opserver to AD group'
Finding latest package for step: Get SQL Server names
Selected 'Powershell.Infrastructure.Deployment' version '1.1.109' for 'Get SQL Server names'
Finding latest package for step: Configure Opserver
Selected 'Powershell.Infrastructure.Deployment' version '1.1.109' for 'Configure Opserver'
Finding latest package for step: Complete Autoscaling Lifecycle Action
Selected 'Powershell.Infrastructure.Deployment' version '1.1.109' for 'Complete Autoscaling Lifecycle Action'
Selected the release plan for Channel 'Default' - it is a perfect match
Using version number provided on command-line: 1.1.0.16
Release plan for Opserver 1.1.0.16

Channel: 'Default' (this is the default channel)

  #   Name                                    Version    Source             Version rules      
  --- --------------------------------------- ---------- ------------------ -------------------
  1   Add opserver to AD group                1.1.109    Latest available   Allow any version 
  2   Get SQL Server names                    1.1.109    Latest available   Allow any version 
  3   Configure IIS site                      1.1.0.16   User specified     Allow any version
  4   Configure Opserver                      1.1.109    Latest available   Allow any version
  5   Complete Autoscaling Lifecycle Action   1.1.109    Latest available   Allow any version
  6   Notify Dispatch                         1.1.109    Latest available   Allow any version

When using octopusCreateRelease:

def packages = [
                        [packageName: "StackExchange.Opserver", packageReferenceName: "StackExchange.Opserver", packageVersion: "${env.VERSION}"]
                    ]
                    octopusCreateRelease \
                        toolId: 'windows-octo', \
                        serverId: 'octopus-server', \
                        spaceId: 'Spaces-1', \
                        project: 'Opserver', \
                        releaseVersion: "${env.VERSION}", \
                        packageConfigs: packages, \
                        deployThisRelease: true, \
                        cancelOnTimeout: false, \
                        waitForDeployment: true, \
                        deploymentTimeout: '00:15:00', \
                        environment: 'test', \
                        jenkinsUrlLinkback: true, \
                        releaseNotes: true, \
                        releaseNotesSource: 'scm'

it generates:

D:\Tools\OctopusTools\9.0.0\octo.exe create-release --version 1.1.0.13 --channel Default --deployTo test --progress --releaseNotes "some notes" --package StackExchange.Opserver:StackExchange.Opserver:1.1.0.13 --project Opserver --server https://octopus-server/ --apiKey ******** --space Spaces-1 --deploymentTimeout 00:15:00 --ignoreSslErrors

But the packages always show Latest Available instead of User Specified.

Finding latest package for step: Add opserver to AD group
Selected 'Powershell.Infrastructure.Deployment' version '1.1.109' for 'Add opserver to AD group'
Finding latest package for step: Get SQL Server names
Selected 'Powershell.Infrastructure.Deployment' version '1.1.109' for 'Get SQL Server names'
Finding latest package for step: Configure IIS site
Selected 'StackExchange.Opserver' version '1.1.0.13' for 'Configure IIS site'
Finding latest package for step: Configure Opserver
Selected 'Powershell.Infrastructure.Deployment' version '1.1.109' for 'Configure Opserver'
Finding latest package for step: Complete Autoscaling Lifecycle Action
Selected 'Powershell.Infrastructure.Deployment' version '1.1.109' for 'Complete Autoscaling Lifecycle Action'
Finding latest package for step: Notify Dispatch
Selected 'Powershell.Infrastructure.Deployment' version '1.1.109' for 'Notify Dispatch'
Using version number provided on command-line: 1.1.0.15
Release plan for Opserver 1.1.0.15

  #   Name                                    Version    Source             Version rules      
  --- --------------------------------------- ---------- ------------------ -------------------
  1   Add opserver to AD group                1.1.104    Latest available   Allow any version  
  2   Get SQL Server names                    1.1.104    Latest available   Allow any version  
  3   Configure IIS site                      1.1.0.13   Latest available   Allow any version  
  4   Configure Opserver                      1.1.104    Latest available   Allow any version  
  5   Complete Autoscaling Lifecycle Action   1.1.104    Latest available   Allow any version  
  6   Notify Dispatch                         1.1.104    Latest available   Allow any version

With the code the way it is currently, it seems the package code doesn't match the format here: https://octopus.com/docs/octopus-rest-api/octopus-cli/create-release

--package=VALUE        [Optional] Version number to use for a package
                             in the release. Format: StepName:Version or
                             PackageID:Version or
                             StepName:PackageName:Version. StepName,
                             PackageID, and PackageName can be replaced with
                             an asterisk. An asterisk will be assumed for
                             StepName, PackageID, or PackageName if they are
                             omitted.

It looks like the format it's trying to match is StepName:PackageName:Version, but the names in the package map don't match those names. It expects packageName, packageReferenceName and packageVersion.

As an experiment, I tried

[packageName: "Configure IIS site", packageReferenceName: "StackExchange.Opserver", packageVersion: "${env.VERSION}"]

which generates

D:\Tools\OctopusTools\9.0.0\octo.exe create-release --version 1.1.0.15 --channel Default --deployTo test --progress --releaseNotes "some notes" --package "Configure IIS site:StackExchange.Opserver:1.1.0.15" --project Opserver --server https://octopus-server/ --apiKey ******** --space Spaces-1 --deploymentTimeout 00:15:00 --ignoreSslErrors

but that still shows

3   Configure IIS site                      1.1.0.15   Latest available   Allow any version

Is this a bug?
How do I get the release to be created with a specific package and not just choosing the latest when using octopusCreateRelease?
@paulmilbank paulmilbank changed the title Jenkins createRelease not using UserSpecified package Jenkins createRelease not using User Specified package May 2, 2023
@paulmilbank
Copy link
Author

paulmilbank commented May 3, 2023 •
edited
Loading

Did some more digging, if I use additionalArgs to pass in --package=StackExchange.Opserver:1.1.0.17 the generated command becomes

D:\Tools\OctopusTools\9.0.0\octo.exe create-release --version 1.1.0.17 --channel Default --deployTo test --progress --releaseNotes "some notes" --project Opserver --server https://octopus-server/ --apiKey ******** --space Spaces-1 --deploymentTimeout 00:15:00 --ignoreSslErrors --package=StackExchange.Opserver:1.1.0.17

That gives the expected result of the Stackexchange.Opserver package being User Specified

The package version for some steps was not specified. Going to try and resolve those automatically...
Finding latest package for step: Add opserver to AD group
Selected 'Powershell.Infrastructure.Deployment' version '1.1.110' for 'Add opserver to AD group'
Finding latest package for step: Get SQL Server names
Selected 'Powershell.Infrastructure.Deployment' version '1.1.110' for 'Get SQL Server names'
Finding latest package for step: Configure Opserver
Selected 'Powershell.Infrastructure.Deployment' version '1.1.110' for 'Configure Opserver'
Finding latest package for step: Complete Autoscaling Lifecycle Action
Selected 'Powershell.Infrastructure.Deployment' version '1.1.110' for 'Complete Autoscaling Lifecycle Action'
Finding latest package for step: Notify Dispatch
Selected 'Powershell.Infrastructure.Deployment' version '1.1.110' for 'Notify Dispatch'
Using version number provided on command-line: 1.1.0.17
Release plan for Opserver 1.1.0.17
Channel: 'Default' (this is the default channel)

  #   Name                                    Version    Source             Version rules      
  --- --------------------------------------- ---------- ------------------ -------------------
  1   Add opserver to AD group                1.1.110    Latest available   Allow any version  
  2   Get SQL Server names                    1.1.110    Latest available   Allow any version  
  3   Configure IIS site                      1.1.0.17   User specified     Allow any version  
  4   Configure Opserver                      1.1.110    Latest available   Allow any version  
  5   Complete Autoscaling Lifecycle Action   1.1.110    Latest available   Allow any version  
  6   Notify Dispatch                         1.1.110    Latest available   Allow any version

Looking at

octopus-jenkins-plugin/src/main/java/hudson/plugins/octopusdeploy/OctopusDeployReleaseRecorder.java

Line 388 in d13768b

if (StringUtils.isNotBlank(pkg.getPackageReferenceName())) {
, it should be possible to have just packageName and packageVersion which should generate that --package=packageName:packageVersion format.

But if I leave packageReferenceName out of the packages map, I get an error. Possibly because the Packages constructor takes 3 args

octopus-jenkins-plugin/src/main/java/hudson/plugins/octopusdeploy/PackageConfiguration.java

Line 43 in d13768b

public PackageConfiguration(String packageName, String packageReferenceName, String packageVersion) {
.

There is also a log statement here:

octopus-jenkins-plugin/src/main/java/hudson/plugins/octopusdeploy/OctopusDeployReleaseRecorder.java

Line 492 in d13768b

log.info("\t" + pc.getPackageName() + "\t" + pc.getPackageReferenceName() + "\tv" + pc.getPackageVersion());
that seems to expect all three. So if packageReferenceName was null, that would cause errors.

The stacktrace from not having the packageReferenceName suggests that is an issue.

 java.lang.NullPointerException
	at hudson.plugins.octopusdeploy.PackageConfiguration.<init>(PackageConfiguration.java:45)
Caused: java.lang.reflect.InvocationTargetException
	at jdk.internal.reflect.GeneratedConstructorAccessor949.newInstance(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
	at org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:330)
Caused: java.lang.IllegalArgumentException: Could not instantiate {packageVersion=1.1.0.9, packageName=StackExchange.Opserver} for hudson.plugins.octopusdeploy.PackageConfiguration
	at org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:334)
	at org.jenkinsci.plugins.structs.describable.DescribableModel.coerce(DescribableModel.java:474)
	at org.jenkinsci.plugins.structs.describable.DescribableModel.coerceList(DescribableModel.java:585)
	at org.jenkinsci.plugins.structs.describable.DescribableModel.coerce(DescribableModel.java:458)
	at org.jenkinsci.plugins.structs.describable.DescribableModel.injectSetters(DescribableModel.java:429)
	at org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:331)
Caused: java.lang.IllegalArgumentException: Could not instantiate {cancelOnTimeout=false, deployThisRelease=true, deploymentTimeout=00:15:00, environment=test, jenkinsUrlLinkback=true, packageConfigs=[{packageName=StackExchange.Opserver, packageVersion=1.1.0.9}], project=Opserver, releaseNotes=true, releaseNotesSource=scm, releaseVersion=1.1.0.9, serverId=rktapps-octopus, spaceId=Spaces-1, toolId=windows-octo} for hudson.plugins.octopusdeploy.OctopusDeployReleaseRecorder
	at org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:334)
	at org.jenkinsci.plugins.structs.describable.UninstantiatedDescribable.instantiate(UninstantiatedDescribable.java:208)
	at org.jenkinsci.plugins.structs.describable.DescribableModel.coerce(DescribableModel.java:466)
	at org.jenkinsci.plugins.structs.describable.DescribableModel.buildArguments(DescribableModel.java:409)
	at org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:329)
Caused: java.lang.IllegalArgumentException: Could not instantiate {delegate=@octopusCreateRelease(cancelOnTimeout=false,deployThisRelease=true,deploymentTimeout=00:15:00,environment=test,jenkinsUrlLinkback=true,packageConfigs=[{packageName=StackExchange.Opserver, packageVersion=1.1.0.9}],project=Opserver,releaseNotes=true,releaseNotesSource=scm,releaseVersion=1.1.0.9,serverId=rktapps-octopus,spaceId=Spaces-1,toolId=windows-octo)} for org.jenkinsci.plugins.workflow.steps.CoreStep
	at org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:334)
	at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:305)
	at org.jenkinsci.plugins.workflow.cps.DSL.invokeDescribable(DSL.java:502)
	at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:199)
	at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:124)
	at jdk.internal.reflect.GeneratedMethodAccessor803.invoke(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:41)
	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:47)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116)
	at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:180)
	at org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:23)
	at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:163)
	at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:178)
	at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:182)
	at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:152)
	at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:152)
	at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:17)
Caused: java.lang.IllegalArgumentException: Failed to prepare octopusCreateRelease step
	at org.jenkinsci.plugins.workflow.cps.DSL.invokeDescribable(DSL.java:504)
	at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:199)
	at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:124)
	at jdk.internal.reflect.GeneratedMethodAccessor803.invoke(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:41)
	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:47)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116)
	at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:180)
	at org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:23)
	at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:163)
	at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:178)
	at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:182)
	at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:152)
	at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:152)
	at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:17)
	at WorkflowScript.run(WorkflowScript:60)
	at ___cps.transform___(Native Method)
	at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:90)
	at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:116)
	at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:85)
	at jdk.internal.reflect.GeneratedMethodAccessor363.invoke(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)
	at com.cloudbees.groovy.cps.impl.CollectionLiteralBlock$ContinuationImpl.dispatch(CollectionLiteralBlock.java:55)
	at com.cloudbees.groovy.cps.impl.CollectionLiteralBlock$ContinuationImpl.item(CollectionLiteralBlock.java:45)
	at jdk.internal.reflect.GeneratedMethodAccessor367.invoke(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)
	at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21)
	at com.cloudbees.groovy.cps.Next.step(Next.java:83)
	at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:152)
	at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:146)
	at org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:136)
	at org.codehaus.groovy.runtime.GroovyCategorySupport.use(GroovyCategorySupport.java:275)
	at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:146)
	at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:18)
	at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:51)
	at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:187)
	at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:420)
	at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:330)
	at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:294)
	at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:67)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:139)
	at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
	at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:68)
	at jenkins.util.ErrorLoggingExecutorService.lambda$wrap$0(ErrorLoggingExecutorService.java:51)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:829)

@paulmilbank paulmilbank mentioned this issue May 3, 2023
Open
@paulmilbank
Copy link
Author

paulmilbank commented May 3, 2023 •
edited
Loading

Looks like if I specifically set the packageReferenceName to a blank string like so

def packages = [
                        [packageName: "StackExchange.Opserver", packageReferenceName: "", packageVersion: "${env.VERSION}"]
                    ]

                    octopusCreateRelease \
                        toolId: 'windows-octo', \
                        serverId: 'rktapps-octopus', \
                        spaceId: 'Spaces-1', \
                        project: 'Opserver', \
                        releaseVersion: "${env.VERSION}", \
                        packageConfigs: packages, \
                        deployThisRelease: true, \
                        cancelOnTimeout: false, \
                        waitForDeployment: true, \
                        deploymentTimeout: '00:15:00', \
                        environment: 'test', \
                        jenkinsUrlLinkback: true, \
                        releaseNotes: true, \
                        releaseNotesSource: 'scm'

The octo CLI command also looks correct and I get a User Specified package
Output:

INFO: Package Configurations:
INFO: 	StackExchange.Opserver		v1.1.0.18
INFO: =======================

[] $ D:\Tools\OctopusTools\9.0.0\octo.exe create-release --version 1.1.0.18 --channel Default --deployTo test --progress --releaseNotes "some-notes" --package StackExchange.Opserver:1.1.0.18 --project Opserver --server https://octopus-server/ --apiKey ******** --space Spaces-1 --deploymentTimeout 00:15:00 --ignoreSslErrors

Octopus CLI, version 9.0.0
Detected automation environment: "Jenkins"
Found space: Default (Spaces-1)
Space name specified, process is now running in the context of space: Default
Handshaking with Octopus Server: https://octopus-server/
Handshake successful. Octopus version: 2022.1.2495; API version: 3.0.0
Authenticated as: Jenkins (a service account)
Found environment: test (Environments-1)
This Octopus Server supports channels
Found project: Opserver (Projects-82)
Building release plan for channel 'Default'...
Found channel: Default (Channels-83)
Finding deployment process...
Finding release template...

The package version for some steps was not specified. Going to try and resolve those automatically...
Finding latest package for step: Add opserver to AD group
Selected 'Powershell.Infrastructure.Deployment' version '1.1.110' for 'Add opserver to AD group'
Finding latest package for step: Get SQL Server names
Selected 'Powershell.Infrastructure.Deployment' version '1.1.110' for 'Get SQL Server names'
Finding latest package for step: Configure Opserver
Selected 'Powershell.Infrastructure.Deployment' version '1.1.110' for 'Configure Opserver'
Finding latest package for step: Complete Autoscaling Lifecycle Action
Selected 'Powershell.Infrastructure.Deployment' version '1.1.110' for 'Complete Autoscaling Lifecycle Action'
Finding latest package for step: Notify Dispatch
Selected 'Powershell.Infrastructure.Deployment' version '1.1.110' for 'Notify Dispatch'

Using version number provided on command-line: 1.1.0.18

Release plan for Opserver 1.1.0.18
Channel: 'Default' (this is the default channel)

  #   Name                                    Version    Source             Version rules      
  --- --------------------------------------- ---------- ------------------ -------------------
  1   Add opserver to AD group                1.1.110    Latest available   Allow any version  
  2   Get SQL Server names                    1.1.110    Latest available   Allow any version  
  3   Configure IIS site                      1.1.0.18   User specified     Allow any version  
  4   Configure Opserver                      1.1.110    Latest available   Allow any version  
  5   Complete Autoscaling Lifecycle Action   1.1.110    Latest available   Allow any version  
  6   Notify Dispatch                         1.1.110    Latest available   Allow any version

So that is a possible workaround to this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@paulmilbank