[JIRA] (JENKINS-59401) After Upgrade to Inedo Plugin 2.5.0 could not create package

2019-12-23 Thread andrew.sum...@xtra.co.nz (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Sumner closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59401  
 
 
  After Upgrade to Inedo Plugin 2.5.0 could not create package   
 

  
 
 
 
 

 
Change By: 
 Andrew Sumner  
 
 
Status: 
 Resolved Closed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201958.1568681322000.15316.1577169480515%40Atlassian.JIRA.


[JIRA] (JENKINS-59401) After Upgrade to Inedo Plugin 2.5.0 could not create package

2019-12-23 Thread andrew.sum...@xtra.co.nz (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Sumner resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 This is fixed by release 3.0.0 - unfortunately this is a breaking release.  I've been doing some work to align the BuildMaster Jenkins Extension and the Jenkins BuildMaster Plugin and took the opportunity to finish of change back from package to build api and rename all parameters and exported variables.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-59401  
 
 
  After Upgrade to Inedo Plugin 2.5.0 could not create package   
 

  
 
 
 
 

 
Change By: 
 Andrew Sumner  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
You received 

[JIRA] (JENKINS-59401) After Upgrade to Inedo Plugin 2.5.0 could not create package

2019-09-18 Thread andrew.sum...@xtra.co.nz (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Sumner commented on  JENKINS-59401  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: After Upgrade to Inedo Plugin 2.5.0 could not create package   
 

  
 
 
 
 

 
 Odd, should have been a fairly minor change, I did upgrade some dependencies.  Will take me a few days to get to it as my server running BuildMaster has had a melt down   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201958.1568681322000.247.1568802480792%40Atlassian.JIRA.


[JIRA] (JENKINS-59401) After Upgrade to Inedo Plugin 2.5.0 could not create package

2019-09-16 Thread jstarb...@scisolutions.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jon Starbird created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59401  
 
 
  After Upgrade to Inedo Plugin 2.5.0 could not create package   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Andrew Sumner  
 
 
Components: 
 inedo-buildmaster-plugin  
 
 
Created: 
 2019-09-17 00:48  
 
 
Environment: 
 Jenkins 2.176.3  Inedo Buildmaster plugin 2.5.0  BuildMaster 6.1.10   
 
 
Priority: 
  Major  
 
 
Reporter: 
 Jon Starbird  
 

  
 
 
 
 

 
 After updating to plugin 2.5.0 it fails to create a build in BuildMaster.  I don't get an error I merely get a msg of:   

 

[2019-09-16T22:36:13.574Z] [BuildMaster] Create build for the PNM Main and Admin application, release 15.6.0
Conversion = 'F'
 

   I was previously on 2.4.0 and after downgrading the plugin it does work again so the plugin update is  the only change. This is using Jenkinsfile and the request to do create a build is like this: 

 

 buildMasterWithApplicationRelease(applicationId: "${env.BuildMaster_appId}", deployableId: "${env.BuildMaster_deployableId}") { buildMasterWithApplicationRelease(applicationId: "${env.BuildMaster_appId}", deployableId: "${env.BuildMaster_deployableId}") { script { def verstr = gitprops.GitVersion_FullSemVer if (env.BRANCH_NAME == 'master') { verstr = gitprops.GitVersion_MajorMinorPatch } def (reponame,jobname) = JOB_NAME.split('/') def bmjenkinsjobname= "${reponame}/job/${jobname}"