[JIRA] (JENKINS-61868) BuildMaster plugin - Cannot create first build of release for application
Title: Message Title Jon Starbird created an issue Jenkins / JENKINS-61868 BuildMaster plugin - Cannot create first build of release for application Issue Type: Bug Assignee: Andrew Sumner Components: inedo-buildmaster-plugin Created: 2020-04-10 15:49 Environment: Jenkins 2.222.1 BuildMaster Plugin 3.1.0 BuildMaster 6.1.26 Priority: Minor Reporter: Jon Starbird Started a new Release in BuildMaster for application. Have the BuildMaster Release Parameter field setup for the app. In job, have Create Build step. When ran, select the app, release, then try to run. hit error - FATAL: Null value not allowed as an environment variable: BUILDMASTER_LATEST_BUILD_NUMBER java.lang.IllegalArgumentException: Null value not allowed as an environment variable: BUILDMASTER_LATEST_BUILD_NUMBER at hudson.EnvVars.put(EnvVars.java:379) at com.inedo.buildmaster.jenkins.BuildMasterReleaseParameterValue.buildEnvironment(BuildMasterReleaseParameterValue.java:71) at org.jenkinsci.plugins.envinject.util.RunHelper.getBuildVariables(RunHelper.java:88) at org.jenkinsci.plugins.envinject.util.RunHelper.getBuildVariables(RunHelper.java:153) at org.jenkinsci.plugins.envinject.EnvInjectListener.setUpEnvironmentWithoutJobPropertyObject(EnvInjectListener.java:233) at org.jenkinsci.plugins.envinject.EnvInjectListener.setUpEnvironment(EnvInjectListener.java:49) at hudson.model.AbstractBuild$AbstractBuildExecution.createLauncher(AbstractBuild.java:542) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:462) at hudson.model.Run.execute(Run.java:1856) at
[JIRA] (JENKINS-61338) BuildMaster plugin Deploy to Stage not passing variables.
Title: Message Title
Jon Starbird created an issue
Jenkins / JENKINS-61338
BuildMaster plugin Deploy to Stage not passing variables.
Issue Type:
Bug
Assignee:
Andrew Sumner
Components:
inedo-buildmaster-plugin
Created:
2020-03-04 22:46
Environment:
Jenkins 2.204.3 BuildMaster plugin 3.1.0 BuildMaster 6.1.26
Priority:
Major
Reporter:
Jon Starbird
Deploy BuildMaster Build To Stage doesn't seem to be passing variables. I hadn't used this functionality before for this function but have some new jobs I was trying to use it with. These are being entered via Classic view so entered into the Variables field. I've tried the following formats: varname=$Client_Id varname=${Client_id} varname=${ENV,var="Client_Id"} The create build step works fine with the second format. If this is a bug would there be a chance you could provide a fix compatible with 6.1.26 as I have a legacy extension in BuildMaster that I will not be able to replace for a couple of months.
Add Comment
[JIRA] (JENKINS-60613) Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0
Title: Message Title Jon Starbird commented on JENKINS-60613 Re: Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0 No worries. I'm not ready to move to 6.2.x of BM yet anyway. thanks for the update. Good luck with the move. 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.203842.1577724088000.6622.1582663980096%40Atlassian.JIRA.
[JIRA] (JENKINS-60613) Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0
Title: Message Title Jon Starbird commented on JENKINS-60613 Re: Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0 actually that would be great. just the other day I was thinking about asking if selecting builds would be possible but it wasn't a critical thing 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.203842.1577724088000.7437.1580227260205%40Atlassian.JIRA.
[JIRA] (JENKINS-60613) Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0
Title: Message Title Jon Starbird commented on JENKINS-60613 Re: Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0 Put on my test server, works great. Not sure you need to do it any differently but up to you. Thank you! 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.203842.1577724088000.7352.1578939120129%40Atlassian.JIRA.
[JIRA] (JENKINS-60613) Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0
Title: Message Title Jon Starbird commented on JENKINS-60613 Re: Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0 Great. I'll keep an eye out for it. Thanks! 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.203842.1577724088000.4960.1578509280126%40Atlassian.JIRA.
[JIRA] (JENKINS-60613) Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0
Title: Message Title Jon Starbird commented on JENKINS-60613 Re: Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0 I sort of thought doing that might prove difficult. It's solvable in other ways so it really is not a big deal. I had used that plugin before on an older server but I had to drop it as it ended up causing the server to become corrupted, or rather the scriptler portion. I never used the scriptler portion but it eventually made it so the Jenkins server could not be upgraded. I never had a chance to dig real deep into it. Then with Scriptler is of course a security issue plugin which here I cannot risk using. Anyway, thanks for spending the time to look into it. Have a great year! 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.203842.1577724088000.2927.1578334980351%40Atlassian.JIRA.
[JIRA] (JENKINS-60613) Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0
Title: Message Title Jon Starbird commented on JENKINS-60613 Re: Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0 Yes, having it allow selecting both. The options you listed provide the right method to do it so, no, I don't think there is a need to allow using custom variables in the Create Build or Deploy Build tasks. Thanks. 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.203842.1577724088000.1279.1577836440136%40Atlassian.JIRA.
[JIRA] (JENKINS-60613) Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0
Title: Message Title Jon Starbird commented on JENKINS-60613 Re: Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0 Using the Env vars as build params is what is going to really work. This will allow me to use only 1 or 2 deployment jobs for all the apps instead of having to use one for each app. Not sure if you could make the BM parameter to have two inputs to allow the app and release number to be selected/defined at run time. You can just define string var params for them but having the app list pre-populated would just help to ensure users put the right values in. But this only applies to being able to have a single Deployment Jobs in Jenkins that would allow you to start a deployment. 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.203842.1577724088000.1242.1577809080238%40Atlassian.JIRA.
[JIRA] (JENKINS-60613) Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0
Title: Message Title Jon Starbird commented on JENKINS-60613 Re: Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0 I hadn't realized you had added the job param option. That actually might do the trick. That or the env vars as you mentioned would also solve the issue, just didn't occur to me to do that. as to other new features, nothing I can currently think of. Thanks! 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.203842.1577724088000.1128.1577755380163%40Atlassian.JIRA.
[JIRA] (JENKINS-60613) Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0
Title: Message Title Jon Starbird created an issue Jenkins / JENKINS-60613 Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0 Issue Type: Bug Assignee: Andrew Sumner Components: inedo-buildmaster-plugin Created: 2019-12-30 16:41 Environment: Jenkins 2.204.1 BuildMaster plugin 3.0.0 Priority: Critical Reporter: Jon Starbird After upgrading to 3.0 of the plugin I can no longer specify the Release Number with a variable as I could before in the Create Build and Deploy Build tasks. This in the classic Jenkins job mode. We run multiple release builds simultaneously at times so I need to be able to specify it via a variable otherwise we have to have have extra jobs and hard code the release number as we cannot use Latest Active Release. Having the ability to override it in the both tasks or even better would be to have the override in the Inject BuildMaster release details step that would then set the buildmaster_release_number variable for the other BM tasks. I have not tried yet in declarative script mode yet but this would be needed there as well. I am going to have to downgrade to the older 2.4.0 version of the plugin for now but I don't know if that version will work with BuildMaster 6.2 when it comes out.
[JIRA] (JENKINS-58954) Durable-task-plugin Powershell step returnStdOut no longer working
Title: Message Title Jon Starbird commented on JENKINS-58954 Re: Durable-task-plugin Powershell step returnStdOut no longer working Devin Nusbaum thanks for the update. I hadn't noticed the case so I will check that. 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.201301.156588437.7426.1574806020143%40Atlassian.JIRA.
[JIRA] (JENKINS-59401) After Upgrade to Inedo Plugin 2.5.0 could not create package
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}"
[JIRA] (JENKINS-58954) Durable-task-plugin Powershell step returnStdOut no longer working
Title: Message Title Jon Starbird created an issue Jenkins / JENKINS-58954 Durable-task-plugin Powershell step returnStdOut no longer working Issue Type: Bug Assignee: Unassigned Components: durable-task-plugin Created: 2019-08-15 15:52 Environment: Jenkins 2.176.2 Durable Task Plugin 1.30 Priority: Minor Reporter: Jon Starbird Not sure if this started in 1.30 as I didn't notice it until today. Is returnStdOut no longer supported? I didn't find any mention anywhere of it being removed. Scripts still run of course but nothing is printed out from the script run even if the Powershell script has write statements. Now getting this warning - WARNING: Unknown parameter(s) found for class type 'org.jenkinsci.plugins.workflow.steps.durable_task.PowershellScriptStep': returnStdOut Add Comment
[JIRA] (JENKINS-57438) Blue Ocean multibranch scan queuing should not add to queue if job already queued
Title: Message Title Jon Starbird assigned an issue to Unassigned Jenkins / JENKINS-57438 Blue Ocean multibranch scan queuing should not add to queue if job already queued Change By: Jon Starbird Component/s: bitbucket-branch-source-plugin Component/s: bitbucket-plugin Component/s: blueocean-plugin Component/s: multibranch-scan-webhook-trigger-plugin Assignee: Jon Starbird Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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
[JIRA] (JENKINS-57438) Blue Ocean multibranch scan queuing should not add to queue if job already queued
Title: Message Title Jon Starbird commented on JENKINS-57438 Re: Blue Ocean multibranch scan queuing should not add to queue if job already queued Igal Gluh thanks, I wasn't sure which part was controlling this. Thanks for your time and changing the component. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.199251.1557771219000.1845.1557780720265%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57438) Blue Ocean multibranch scan queuing should not add to queue if job already queued
Title: Message Title Jon Starbird updated an issue Jenkins / JENKINS-57438 Blue Ocean multibranch scan queuing should not add to queue if job already queued Change By: Jon Starbird Attachment: j1.PNG Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.199251.1557771219000.1805.1557779160219%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57438) Blue Ocean multibranch scan queuing should not add to queue if job already queued
Title: Message Title Jon Starbird commented on JENKINS-57438 Re: Blue Ocean multibranch scan queuing should not add to queue if job already queued Not sure how much you want but gave the setting for polling. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.199251.1557771219000.1807.1557779160257%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57438) Blue Ocean multibranch scan queuing should not add to queue if job already queued
Title: Message Title Jon Starbird created an issue Jenkins / JENKINS-57438 Blue Ocean multibranch scan queuing should not add to queue if job already queued Issue Type: Bug Assignee: Igal Gluh Components: multibranch-scan-webhook-trigger-plugin Created: 2019-05-13 18:13 Environment: Jenkins - 2.164.2 - blueocean multibranch builds Bitbucket Cloud Priority: Major Reporter: Jon Starbird Apologies if I did not pick the correct component for this, please change to the correct one if needed. When using Polling instead of build requests from Bitbucket, business environment requirement, Jenkins will add repeated multibranch scans to the job queue even when one is already queued. This occurs because Bitbucket cloud has limitations on API use so if enough requests come in the queue gets back logged. Jenkins should not be adding requests for multibranch scans to the queue if one already exists for that job. Since the scan only uses one executor on the main server this causes the queue to fill up and slow builds down dramatically.
[JIRA] (JENKINS-56351) Cannot create new job using Bitbucket Cloud
Title: Message Title Jon Starbird updated JENKINS-56351 apologies. Happened to be talking to one of the dev managers and he had changed the permissions on the user used for Bitbucket cloud access. Issue is resolved. Jenkins / JENKINS-56351 Cannot create new job using Bitbucket Cloud Change By: Jon Starbird Status: Open Fixed but Unreleased Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56351) Cannot create new job using Bitbucket Cloud
Title: Message Title Jon Starbird created an issue Jenkins / JENKINS-56351 Cannot create new job using Bitbucket Cloud Issue Type: Bug Assignee: Unassigned Components: bitbucket-branch-source-plugin Created: 2019-03-01 19:56 Environment: Bitbucket Cloud Jenkins 2.150.3 Bitbucket Source plugin 2.4.2 Priority: Blocker Reporter: Jon Starbird Not sure where the issue is here but when attempting to create a new Pipeline in BlueOcean it is not correctly seeing our Team. It will only show the user, this was working fine and now it does not. Then it also won't let me force it or add anything either. The user being used is part of the team and hasn't changed at all not even the password. The Bitbucket permissions for the user have not changed at all either. I also tried to create one using the non-blue ocean Bitbucket Mulit branch job type and with that it will not allow me to select a Repo at all, doesn't even show the Field repository any longer. Our Jenkins server is internally available only so I cannot setup Bitbucket to push to it so this is a critical issue.
[JIRA] (JENKINS-55395) Allow plugins to add links to Blue Ocean Dashboard
Title: Message Title Jon Starbird created an issue Jenkins / JENKINS-55395 Allow plugins to add links to Blue Ocean Dashboard Issue Type: Improvement Assignee: Unassigned Components: blueocean-plugin Created: 2019-01-04 01:31 Priority: Major Reporter: Jon Starbird Currently Blue Ocean doesn't allow any way to add links to the Dashboard, be they HTML reports or just Sidebar links. Please add the ability for plugins to add links to the dashboards. It should allow links to be added to the main dashboard, the project dashboard and the build dashboard. Add Comment
[JIRA] (JENKINS-50976) At end of build plugin is querying BuildMaster for apps deployable info
Title: Message Title Jon Starbird commented on JENKINS-50976 Re: At end of build plugin is querying BuildMaster for apps deployable info I haven't seen it recently but It wasn't happening all the time. Go ahead and close this out, I think, if you want, and if it happens again I can submit a new one. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54469) Unable to set Thread Executor Size when configuring Jira Plugin
Title: Message Title Jon Starbird created an issue Jenkins / JENKINS-54469 Unable to set Thread Executor Size when configuring Jira Plugin Issue Type: Bug Assignee: Unassigned Components: jira-plugin Created: 2018-11-05 17:13 Environment: Jira Plugin 3.0.4 Jenkins 2.138.2 Windows 2016 Priority: Minor Reporter: Jon Starbird Setting up a new Jenkins server and adding the Jira configuration info in the main Admin Configuration settings. There is a place to add the Thread Executor Size but it will not accept any value nor blank. Regardless of value put in you cannot Validate and get the error that the Thread Executor Size must be at least 1. I've tried setting it 0, 1, 9, 10, 12 and also blank but always get the same error. You can still save changes but cannot validate. Add Comment
[JIRA] (JENKINS-54286) Unable to use variable tokens as build property values in Create Package in Declarative Script
Title: Message Title Jon Starbird commented on JENKINS-54286 Re: Unable to use variable tokens as build property values in Create Package in Declarative Script I see the issue. I didn't catch the change from SetBuildVariables to PackageVariables. I've updated it and now it is working. Thanks! Sorry for the extra work but much appreciated. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54286) Unable to use variable tokens as build property values in Create Package in Declarative Script
Title: Message Title
Jon Starbird commented on JENKINS-54286
Re: Unable to use variable tokens as build property values in Create Package in Declarative Script
Just the change of the brackets didn't make a difference. I used it just like I posted above but with the ${gitprops.GitVersion_FullSemVer} change. Here is the Jenkins log output for the entire Create Package stage, as you can see the app id and deployable id are set correctly.
[Pipeline] { (Create Buildmaster package)
[Pipeline] wrap
14:29:59 [BuildMaster] Sending POST to http://ca-builder3:8181/api/releases
14:29:59 [BuildMaster] With application/x-www-form-urlencoded content:
14:29:59 [BuildMaster] key=xxx=44=active
14:29:59 [BuildMaster] Inject environment variable BUILDMASTER_APPLICATION_ID=44
14:29:59 [BuildMaster] Inject environment variable BUILDMASTER_RELEASE_NUMBER=1.1.0
14:29:59 [BuildMaster] Inject environment variable BUILDMASTER_DEPLOYABLE_ID=1058
[Pipeline] {
[Pipeline] script
[Pipeline] {
[Pipeline] buildMasterCreatePackage
14:29:59 [BuildMaster] Sending GET to http://ca-builder3:8181/api/json/Applications_GetApplication?API_Key=xxx_Id=44
14:29:59 [BuildMaster] Create BuildMaster package
14:29:59 [BuildMaster] Sending PUT to http://ca-builder3:8181/api/releases/packages/create
14:29:59 [BuildMaster] With application/x-www-form-urlencoded content:
14:29:59 [BuildMaster] key=xxx=44=1.1.0
14:29:59 [BuildMaster] Wait for any active deployments to complete
14:29:59 [BuildMaster] Sending POST to http://ca-builder3:8181/api/releases/packages/deployments
14:29:59 [BuildMaster] With application/x-www-form-urlencoded content:
14:29:59 [BuildMaster] key=xxx=44=1.1.0=pending
14:29:59 [BuildMaster] Sending POST to http://ca-builder3:8181/api/releases/packages/deployments
14:29:59 [BuildMaster] With application/x-www-form-urlencoded content:
14:29:59 [BuildMaster] key=xxx=44=1.1.0=executing
14:29:59 [BuildMaster] Deploy package to next stage
14:29:59 [BuildMaster] Sending PUT to http://ca-builder3:8181/api/releases/packages/deploy
14:29:59 [BuildMaster] With application/x-www-form-urlencoded content:
14:29:59 [BuildMaster] key=xxx=44=1.1.0=181031006
14:30:00 [BuildMaster] Wait till deployment completed
14:30:00 [BuildMaster] Sending POST to http://ca-builder3:8181/api/releases/packages/deployments
14:30:00 [BuildMaster] With application/x-www-form-urlencoded content:
14:30:00 [BuildMaster] key=xxx=44=1.1.0=181031006=17131
14:30:07 [BuildMaster] Sending POST to http://ca-builder3:8181/api/releases/packages/deployments
14:30:07 [BuildMaster] With application/x-www-form-urlencoded content:
14:30:07 [BuildMaster] key=xxx=44=1.1.0=181031006=17131
[JIRA] (JENKINS-54286) Unable to use variable tokens as build property values in Create Package in Declarative Script
Title: Message Title Jon Starbird commented on JENKINS-54286 Re: Unable to use variable tokens as build property values in Create Package in Declarative Script The appid and deployableid are being set at the top of the script in the environment section of the full script. These to values work though, it's getting to the app in BuildMaster. I will try the brackets around the git props and the API logging. I also should have been more clear, the Jenkins job does fail. I only meant I don't get errors about the script itself. It does execute the call to BuildMaster which fails with BuildMaster failing on the passed variables not being set and then the Jenkins job will fail at that stage. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54286) Unable to use variable tokens as build property values in Create Package in Declarative Script
Title: Message Title
Jon Starbird commented on JENKINS-54286
Re: Unable to use variable tokens as build property values in Create Package in Declarative Script
Not working for me, maybe the format isn't right. I tried it with double quotes around the variables as well as the original method of triple single quotes and neither worked. Build_Number and Job_Name are both environment variables but the gitprops.gitversion_fullsemver is from importing the gitversion properties into the job earlier. I do use it elsewhere just fine even here for the ReleaseNumber. Here is what I have currently:
buildMasterWithApplicationRelease(applicationId: "${env.BuildMaster_appId}", deployableId: "${env.BuildMaster_deployableId}") {
script {
BUILDMASTER_PACKAGE_NUMBER = buildMasterCreatePackage applicationId: BUILDMASTER_APPLICATION_ID, deployToFirstStage: true, packageNumber: BUILDMASTER_PACKAGE_NUMBER, releaseNumber: "${gitprops.GitVersion_MajorMinorPatch}",
setBuildVariables: [
preserveVariables: false,
variables: "JenkinsBuildNumber=$BUILD_NUMBER\nBuildVersion=$gitprops.GitVersion_FullSemVer\nJenkinsProject=$JOB_NAME"],
waitTillBuildCompleted: [printLogOnFailure: false]
}
}
When it runs I get no errors on the Jenkins but on the BuildMaster it fails and doesn't show any values for the passed variables.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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.
For more options, visit
[JIRA] (JENKINS-54286) Unable to use variable tokens as build property values in Create Package in Declarative Script
Title: Message Title Jon Starbird commented on JENKINS-54286 Re: Unable to use variable tokens as build property values in Create Package in Declarative Script Andrew Sumner as usual thanks for the quick turnaround! I will test it a bit later today. One important note though, when I installed the update it wiped all the pre-existing variable settings for any existing Classic jobs. Fortunately on this server I only had two but on others it will be many more. Not sure if there is a way to migrate them or not for you, if not having the Warning message about changed formats in the updates area would be helpful. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54286) Unable to use variable tokens as build property values in Create Package in Declarative Script
Title: Message Title
Jon Starbird created an issue
Jenkins / JENKINS-54286
Unable to use variable tokens as build property values in Create Package in Declarative Script
Issue Type:
Bug
Assignee:
Andrew Sumner
Components:
inedo-buildmaster-plugin
Created:
2018-10-27 00:07
Environment:
Jenkins 2.138.2 BM plugin 2.0.2
Priority:
Critical
Reporter:
Jon Starbird
I have job in declarative script and in the create package I need to pass some variables and values but I cannot use Token variables here or at least I have been unable to find a way to use them. I've tried property=${varname} , property =$varname , property = "${varname}" and property = varname but the values are just never replaced with the values of the variables. I also tried setting them to new variables within the script block and then using the above options and again it never replaces them. I can use tokens in the Release Number , app id, deployable id just fine but I cannot as buildvariables. These are dynamic values so they cannot be hard coded. If there is already a way to do this you might want to note it in the docs.
[JIRA] (JENKINS-47792) Job with in queue with status "pending description" do not start
Title: Message Title Jon Starbird commented on JENKINS-47792 Re: Job with in queue with status "pending description" do not start Ok. I seemed to have fixed my issue. I went into the parent job and enabled the block until upstream and downstream, saved. Reopened and disabled them. Then opened each job it was calling and then all of them showed they were being blocked while upstream job was building. I then disabled that flag on all of those jobs and then the build would run properly. It appears that somehow the block upstream flag is set but not shown to be set for the downstream jobs or something along those lines. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47792) Job with in queue with status "pending description" do not start
Title: Message Title Jon Starbird commented on JENKINS-47792 Re: Job with in queue with status "pending description" do not start I'm still having this issue. It does only seem to impact new jobs as I do have other jobs that have not been edited in long time that still work. I am currently up to Jenkins 2.121.3. Also, I had not noticed this before but in the Job queue if I hover over the pending job it says Upstream project of Full Build is already building. That seems like it's not executing because it's waiting for it's parent job to finish. I do not have anything set for any job to wait for upstream jobs. The parent job is set to wait for the downstream job to finish before it continues. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53336) inedo-buildmaster - trigger deployment always returns that job was aborted if job had warnings on BuildMaster
Title: Message Title Jon Starbird commented on JENKINS-53336 Re: inedo-buildmaster - trigger deployment always returns that job was aborted if job had warnings on BuildMaster Andrew, no I would not need that, pass/fail is sufficient. Thanks. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53336) inedo-buildmaster - trigger deployment always returns that job was aborted if job had warnings on BuildMaster
Title: Message Title Jon Starbird created an issue Jenkins / JENKINS-53336 inedo-buildmaster - trigger deployment always returns that job was aborted if job had warnings on BuildMaster Issue Type: Bug Assignee: Andrew Sumner Components: inedo-buildmaster-plugin Created: 2018-08-30 01:33 Environment: BuildMaster 6.0.10 Jenkins 2.121.3 inedo-buildmaster plugin 2.0.1 Priority: Major Reporter: Jon Starbird After called Deploy BuildMaster Package to Stage, it will end up reporting that the BuildMaster job was aborted even though the job wasn't aborted. The job does have warnings but it completes without errors. This causes Jenkins to see the build job as a failure. If a job does not have warning then it completes fine. Add Comment
[JIRA] (JENKINS-53263) indeo-buildmaster Create Package not passing variables
Title: Message Title Jon Starbird commented on JENKINS-53263 Re: indeo-buildmaster Create Package not passing variables Andrew, that did fix it. Thank you so much for the fast turn around! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53263) indeo-buildmaster Create Package not passing variables
Title: Message Title Jon Starbird created an issue Jenkins / JENKINS-53263 indeo-buildmaster Create Package not passing variables Issue Type: Bug Assignee: Andrew Sumner Components: inedo-buildmaster-plugin Created: 2018-08-27 22:53 Environment: Buildmaster 6.0.10 Jenkins 2.121.3 inedo-buildmaster plugin 2.0 Priority: Critical Reporter: Jon Starbird When using the Set Build Variables when using the Create BuildMaster Package call, none of the variables set are sent and set in BuildMaster. I checked the API access log on the BuildMaster side and it does not show any variables being passed with the request. Add Comment
[JIRA] (JENKINS-47792) Job with in queue with status "pending description" do not start
Title: Message Title Jon Starbird commented on JENKINS-47792 Re: Job with in queue with status "pending description" do not start marlene cote so let me understand what you did, see if it works for me, you have Mutli-Job that you just have it do a Trigger/Call Build On another Project and then it works? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47792) Job with in queue with status "pending description" do not start
Title: Message Title Jon Starbird commented on JENKINS-47792 Re: Job with in queue with status "pending description" do not start This has gotten stranger for me. I also have this problem now by just using the Trigger/Call Builds on another project using Parameters. The really strange part is I have other jobs that I use that same call in and they still work. I'm not sure what the issue is. I've tried removing all the params and it will still get stuck. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50976) At end of build plugin is querying BuildMaster for apps deployable info
Title: Message Title Jon Starbird updated an issue Jenkins / JENKINS-50976 At end of build plugin is querying BuildMaster for apps deployable info Change By: Jon Starbird Somehow at the end of a build run the plugin will query BuildMaster. It first queries to get the applications, then it queries the app for it's releases and deployables. It does this over and over and over. For the same app, same deployable. At the point in the Job where this runs the plugin is not being used, it had already been ran earlier in the job. This doesn't happen all the time it seems to only occur if the job's configuration is changed and that change doesn't involve changing anything to do with BuildMaster plugin.Since we have a lot of apps on BuildMaster this causes a build run to take a lot of extra time. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop
[JIRA] (JENKINS-50976) At end of build plugin is querying BuildMaster for apps deployable info
Title: Message Title Jon Starbird updated an issue Jenkins / JENKINS-50976 At end of build plugin is querying BuildMaster for apps deployable info Change By: Jon Starbird Somehow at the end of a build run the plugin will query BuildMaster. It first queries to get all the applications, then it queries each the app for it's releases and deployables. It does this for Every over and over and over. For the same app on BuildMaster even though this job is configured for only 1 app , same deployable .This doesn't happen all the time it seems to only occur if the job's configuration is changed and that change doesn't involve changing anything to do with BuildMaster plugin.Since we have a lot of apps on BuildMaster this causes a build run to take a lot of extra time. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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
[JIRA] (JENKINS-50976) At end of build plugin is querying BuildMaster for apps deployable info
Title: Message Title Jon Starbird updated an issue Jenkins / JENKINS-50976 At end of build plugin is querying BuildMaster for apps deployable info Change By: Jon Starbird Summary: At end of build plugin is querying BuildMaster for every apps deployable info Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50976) At end of build plugin is querying BuildMaster for every apps deployable info
Title: Message Title Jon Starbird created an issue Jenkins / JENKINS-50976 At end of build plugin is querying BuildMaster for every apps deployable info Issue Type: Bug Assignee: Andrew Sumner Components: inedo-buildmaster-plugin Created: 2018-04-24 23:13 Environment: Jenkins 2.89.4 BuildMaster 5.8.3 Jenkins BuildMaster plugin - 1.6 Priority: Major Reporter: Jon Starbird Somehow at the end of a build run the plugin will query BuildMaster. It first queries to get all the applications, then it queries each app for it's releases and deployables. It does this for Every app on BuildMaster even though this job is configured for only 1 app. This doesn't happen all the time it seems to only occur if the job's configuration is changed and that change doesn't involve changing anything to do with BuildMaster plugin. Since we have a lot of apps on BuildMaster this causes a build run to take a lot of extra time. Add Comment
[JIRA] (JENKINS-42041) As a user I want to be able to use Template Variables in Jenkins to pick a specific Release Number in BuildMaster
Title: Message Title Jon Starbird closed an issue as Won't Do This is covered by being able to select the Release in the Trigger Build function as you can bypass the value picked up from the Select Application Function. Jenkins / JENKINS-42041 As a user I want to be able to use Template Variables in Jenkins to pick a specific Release Number in BuildMaster Change By: Jon Starbird Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To
[JIRA] (JENKINS-42041) As a user I want to be able to use Template Variables in Jenkins to pick a specific Release Number in BuildMaster
Title: Message Title Jon Starbird created an issue Jenkins / JENKINS-42041 As a user I want to be able to use Template Variables in Jenkins to pick a specific Release Number in BuildMaster Issue Type: New Feature Assignee: Andrew Sumner Components: inedo-buildmaster-plugin Created: 2017/Feb/14 10:51 PM Environment: Jenkins 2.32.2 BuildMaster Plugin 1.6 BuildMaster 5.6.7 Priority: Major Reporter: Jon Starbird I want to be able to use Jenkins Template variables to pre-set the Release Number based on variables in Jenkins so that you do not have to change multiple entries in the event of multiple active releases in BuildMaster. Using the Template variables allows you to change either a property value or a passed in value to the Jenkins job that can then be used as the Release Number or if you have unique version strings, as we do, this allows you to use those to select the Release Number without having to edit the settings for the Plugin. Add Comment
[JIRA] (JENKINS-42036) As a User I want to be able to pass variables when using the Deploy to Stage function
Title: Message Title Jon Starbird created an issue Jenkins / JENKINS-42036 As a User I want to be able to pass variables when using the Deploy to Stage function Issue Type: New Feature Assignee: Andrew Sumner Components: inedo-buildmaster-plugin Created: 2017/Feb/14 10:05 PM Environment: Jenkins 2.32.2 BuildMaster 5.6.7 BuildMaster Jenkins Pluign 1.6 Priority: Minor Reporter: Jon Starbird Currently you cannot pass any variables to with the Deploy to Stage functionality. While in most cases you most likely would have them already configured there could be some instances of needing to pass some variables. For example, if in one environment you need to deploy to an additional location within that same environment it would be very useful to be able to pass variables from Jenkins if needed. Add Comment
[JIRA] (JENKINS-41772) Json syntax error when selecting Release Number
Title: Message Title Jon Starbird updated an issue Jenkins / JENKINS-41772 Json syntax error when selecting Release Number Change By: Jon Starbird Priority: Major Minor Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41772) Json syntax error when selecting Release Number
Title: Message Title Jon Starbird updated an issue Jenkins / JENKINS-41772 Json syntax error when selecting Release Number Change By: Jon Starbird If selecting a Specific Release Number from the generated drop down of the Select Application function there is a error thrown:com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: Expected STRING but was BEGIN_OBJECTThe Release Number is in the form of 1.0.0.All the drop downs are showing the proper content so the connection to BuildMaster is fine. Note that the step still works despite the error. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41772) Json syntax error when selecting Release Number
Title: Message Title Jon Starbird created an issue Jenkins / JENKINS-41772 Json syntax error when selecting Release Number Issue Type: Bug Assignee: Andrew Sumner Components: inedo-buildmaster-plugin Created: 2017/Feb/06 7:50 PM Environment: Jenkins - 2.23.1 Inedo BuildMaster plugin - 1.6 BuildMaster - 5.6.6 Priority: Major Reporter: Jon Starbird If selecting a Specific Release Number from the generated drop down of the Select Application function there is a error thrown: com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: Expected STRING but was BEGIN_OBJECT The Release Number is in the form of 1.0.0. All the drop downs are showing the proper content so the connection to BuildMaster is fine. Add Comment
[JIRA] (JENKINS-14761) Backslash broken on Properties Content injection
Title: Message Title Jon Starbird closed an issue as Done reopened in error. Closing again. Jenkins / JENKINS-14761 Backslash broken on Properties Content injection Change By: Jon Starbird Status: Reopened Closed Resolution: Done Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-14761) Backslash broken on Properties Content injection
Title: Message Title Jon Starbird commented on JENKINS-14761 Re: Backslash broken on Properties Content injection Apologies, I just saw your old note about the changes for backslash handling. Somehow I missed the message about the changes. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-14761) Backslash broken on Properties Content injection
Title: Message Title Jon Starbird edited a comment on JENKINS-14761 Re: Backslash broken on Properties Content injection This is broken again in 1.93.1 and 1 . 93. Properties like name=somevalue\someothervalue get imported as somevaluesomeothervalue Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-14761) Backslash broken on Properties Content injection
Title: Message Title Jon Starbird reopened an issue This is broken again in 1.93.1. Properties like name=somevalue\someothervalue get imported as somevaluesomeothervalue Jenkins / JENKINS-14761 Backslash broken on Properties Content injection Change By: Jon Starbird Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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
[JIRA] (JENKINS-38633) As a user I want to be able to start a specific stage of a BuildMaster Deployment pipeline.
Title: Message Title Jon Starbird commented on JENKINS-38633 Re: As a user I want to be able to start a specific stage of a BuildMaster Deployment pipeline. Thanks Andrew! Really appreciate you doing the work on both of these issues. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38633) As a user I want to be able to start a specific stage of a BuildMaster Deployment pipeline.
Title: Message Title Jon Starbird commented on JENKINS-38633 Re: As a user I want to be able to start a specific stage of a BuildMaster Deployment pipeline. Thanks Andrew. This will make usage of the plugin much better for our use here. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38633) As a user I want to be able to start a specific stage of a BuildMaster Deployment pipeline.
Title: Message Title Jon Starbird created an issue Jenkins / JENKINS-38633 As a user I want to be able to start a specific stage of a BuildMaster Deployment pipeline. Issue Type: Improvement Assignee: Andrew Sumner Components: inedo-proget-plugin Created: 2016/Sep/30 4:50 PM Environment: BuildMaster 5.4.1 Labels: buildmaster Priority: Major Reporter: Jon Starbird The component for buildmaster doesn't exist so I had to use Proget. Currently the plugin only allows for starting a deployment at the beginning of the pipeline however that limits the usage. I would like to be able to call out a specific stage in the pipeline. For example, if I want Jenkins to build, then have BuildMaster deploy the Integration setup, then have Jenkins run the Integration tests, then assuming the tests pass, have BuildMaster deploy to the next Stage. Another scenario, you may want a certain deployment to a certain stage when another app is successfully, built and tested with Jenkins handling the testing.
[JIRA] (JENKINS-37194) Allow Tokens via Token Macro plugin
Title: Message Title Jon Starbird created an issue Jenkins / JENKINS-37194 Allow Tokens via Token Macro plugin Issue Type: Improvement Assignee: Andrew Sumner Components: inedo-proget-plugin Created: 2016/Aug/05 12:01 AM Priority: Major Reporter: Jon Starbird Allow Tokens via the Token Macros plugin, this would be very useful so that jobs can be used for multiple purposes but also so that versions can be variable defined. Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-37193) inedo-buildmaster-plugin is Not compatible with BuildMaster 5.x
Title: Message Title Jon Starbird created an issue Jenkins / JENKINS-37193 inedo-buildmaster-plugin is Not compatible with BuildMaster 5.x Issue Type: Bug Assignee: Andrew Sumner Components: inedo-proget-plugin Created: 2016/Aug/04 11:51 PM Priority: Major Reporter: Jon Starbird Inedo-buildmaster-plugin component is not listed. When attempting to use the Select BuildMaster Application you get an error "Error: Unable to connect to BuildMaster. java.lang.NullPointerException: null" on the Job Configuration screen. BuildMaster configuration in Admin area is setup and Test Connection from there works. Add Comment
[JIRA] (JENKINS-36730) Need to allow full sem versions like Nuget
Title: Message Title Jon Starbird created an issue Jenkins / JENKINS-36730 Need to allow full sem versions like Nuget Issue Type: Improvement Assignee: Andrew Sumner Components: inedo-proget-plugin Created: 2016/Jul/15 11:07 PM Priority: Blocker Reporter: Jon Starbird Need to allow version like Nuget with the pre-release tags. Only having one version of the package isn't useful if you use Proget for daily build artifact storage. Add Comment This message was sent by Atlassian JIRA
[JIRA] [build-name-setter-plugin] (JENKINS-34195) NPE after upgrade to build-name-setter 1.6.0
Title: Message Title Jon Starbird commented on JENKINS-34195 Re: NPE after upgrade to build-name-setter 1.6.0 I hit this same issue with 1.6.0. The above work around given by Peter does work but this type of bug should be a higher priority than minor, I had to save off practically every single job we have, upwards of 50. I can imagine there are even bigger setups out there than ours so Minor just doesn't cover it so I've bumped it up to Major at the very least. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-name-setter-plugin] (JENKINS-34195) NPE after upgrade to build-name-setter 1.6.0
Title: Message Title Jon Starbird updated an issue Jenkins / JENKINS-34195 NPE after upgrade to build-name-setter 1.6.0 Change By: Jon Starbird Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs-plugin] (JENKINS-33487) Team Foundation Server plugin error about already mapped folder after updating to 4.1.0
Title: Message Title Jon Starbird created an issue Jenkins / JENKINS-33487 Team Foundation Server plugin error about already mapped folder after updating to 4.1.0 Issue Type: Bug Assignee: redsolo Components: tfs-plugin Created: 11/Mar/16 6:07 PM Environment: Jenkins 1.642.2 working version of TFS pluign 4.0 broken version of TFS pluing 4.1.0 Priority: Critical Reporter: Jon Starbird After updating to TFS pluin 4.1.0 a pre-existing Job would no longer work and now throws the error: 14:21:15 Creating workspace 'Hudson-BuildAutomatedTests-MASTER' owned by '172.26.0.40\TFS-SCI_automation1'... 14:21:15 Mapping '$/SCI/BuildProcessTemplates/REWA-Release' to local folder 'D:\buildJobs\workspace\BuildAutomatedTests' in workspace 'Hudson-BuildAutomatedTests-MASTER'... 14:21:16 FATAL: com.microsoft.tfs.core.clients.versioncontrol.exceptions.MappingConflictException: The path D:\buildJobs\workspace\BuildAutomatedTests is already mapped in workspace Hudson-BuildAutomatedTests-MASTER. 14:21:16 java.lang.RuntimeException: com.microsoft.tfs.core.clients.versioncontrol.exceptions.MappingConflictException: The path D:\buildJobs\workspace\BuildAutomatedTests is already mapped in workspace Hudson-BuildAutomatedTests-MASTER.
[JIRA] [email-ext-plugin] (JENKINS-28357) Cannot use Jelly Template after recent 2.40 fix
Title: Message Title Jon Starbird commented on JENKINS-28357 Re: Cannot use Jelly Template after recent 2.40 fix btw Alex, huge thanks for jumping on this so quick! Great to see folks respond quickly to these open source projects, not all do. I know initially this was marked as a blocker issue but you kept at it even once a work around was achieved. So thanks for doing that. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-28357) Cannot use Jelly Template after recent 2.40 fix
Title: Message Title
Jon Starbird commented on JENKINS-28357
Re: Cannot use Jelly Template after recent 2.40 fix
Yes. Then I was entering in the email settings as $ {JELLY_SCRIPT, template=mod1.template}
until I updated to 2.40.1 but the file in email-templates folder has always had the full name with extension.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-28357) Cannot use Jelly Template after recent 2.40 fix
Title: Message Title Jon Starbird commented on JENKINS-28357 Re: Cannot use Jelly Template after recent 2.40 fix No problem. Glad it got figured out. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-28357) Cannot use Jelly Template after recent 2.40 fix
Title: Message Title Jon Starbird commented on JENKINS-28357 Re: Cannot use Jelly Template after recent 2.40 fix It's running as java -jar . Interestingly on both of these machines I was no longer getting the Upgrade message for Jenkins itself within Jenkins for this last update to 1.596.2 so I had to manually download the war files and upgrade that way. After that I upgraded all the plugins that needed upgrading, but I did that the normal way from within Jenkins. My point is that the upgrade to 2.40 happened at the time I did that. No idea what connection could be there but just wanted to mention it since it was an odd situation for the Upgrade notice to not show up in Jenkins. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-28357) Cannot use Jelly Template after recent 2.40 fix
Title: Message Title Jon Starbird commented on JENKINS-28357 Re: Cannot use Jelly Template after recent 2.40 fix I'm not sure where to go next either. Unfortunately company policy prevents me from sharing desktop to an outside entity. I can provide any additional info you think might help. Java version is 1.7, OS is recently updated - like in the last 2 months, do you want a list of all the other plugins? One question, you mentioned before that 2.40 was having the issue of needing the extension but that was for only Groovy, correct? Just wondering why my other system running 2.40 and was never upgraded to 2.40.1, doesn't see the issue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-28357) Cannot use Jelly Template after recent 2.40 fix
Title: Message Title Jon Starbird commented on JENKINS-28357 Re: Cannot use Jelly Template after recent 2.40 fix Yep that fixes the issue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-28357) Cannot use Jelly Template after recent 2.40 fix
Title: Message Title Jon Starbird commented on JENKINS-28357 Re: Cannot use Jelly Template after recent 2.40 fix This particular one is Windows 7 Ultimate. Another one is on Windows 7 Pro with the same Jenkins version but only 2.40 of the plugin, on that one it still works without the extension but I'm not on the 2.40.1. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-28202) groovy templates do not work after upgrading to 2.40
Title: Message Title Jon Starbird commented on JENKINS-28202 Re: groovy templates do not work after upgrading to 2.40 When Jenkins-28202 was fixed for Groovy it seems to have broken Jelly. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-28357) Cannot use Jelly Template after recent 2.40 fix
Title: Message Title
Jon Starbird commented on JENKINS-28357
Re: Cannot use Jelly Template after recent 2.40 fix
So I put the .jelly extension in the call, so $ {JELLY_SCRIPT,template=mod1.template.jelly}
and then it worked. So for some reason it's not adding the extension like it used to.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-28357) Cannot use Jelly Template after recent 2.40 fix
Title: Message Title Jon Starbird commented on JENKINS-28357 Re: Cannot use Jelly Template after recent 2.40 fix yes I did. I'm just about to test again on a blank job so let me see what happens. Before I had only tried the Test Template. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-28202) groovy templates do not work after upgrading to 2.40
Title: Message Title Jon Starbird edited a comment on JENKINS-28202 Re: groovy templates do not work after upgrading to 2.40 WhenJenkins-28202wasfixedforGroovyitseemstohavebrokenJelly. SeeJenkins-28357fortheJellybug. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-28357) Cannot use Jelly Template after recent 2.40 fix
Title: Message Title Jon Starbird commented on JENKINS-28357 Re: Cannot use Jelly Template after recent 2.40 fix is it expecting the Extension in a particular Case? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-28357) Cannot use Jelly Template after recent 2.40 fix
Title: Message Title Jon Starbird commented on JENKINS-28357 Re: Cannot use Jelly Template after recent 2.40 fix So I tried a blank job and it still doesn't find the file. Rebooted the server completely, still doesn't work. Added a line to print the JENKINS_HOME into the email and it shows the Correct Jenkins path where my email-templates folder and the file lives. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-28357) Cannot use Jelly Template after recent 2.40 fix
Title: Message Title
Jon Starbird created an issue
Jenkins / JENKINS-28357
Cannot use Jelly Template after recent 2.40 fix
Issue Type:
Bug
Assignee:
Alex Earl
Components:
email-ext-plugin
Created:
12/May/15 4:39 PM
Environment:
Jenkins LTS 1.596.2, Plugin 2.40.1
Priority:
Blocker
Reporter:
Jon Starbird
When using $ {JELLY_SCRIPT,template=mod1.template}
I get the error that was reported about Groovy scripts for Jenkins-28202, Jelly file [mod1.template] was not found in $JENKINS_HOME/email-templates
Nothing was changed in my environment and the file was used fine before. The file does exist and has the full filename of mod1.template.jelly but now it won't work. Doing a Test email and putting the full filename there it does find it in the correct location it is only when a build fires it off that this is failing.
[JIRA] [email-ext-plugin] (JENKINS-28357) Cannot use Jelly Template after recent 2.40 fix
Title: Message Title Jon Starbird commented on JENKINS-28357 Re: Cannot use Jelly Template after recent 2.40 fix Yep. At least that's what Jenkins is saying it is. Even have a Downgrade to 2.40 button. Let me try downgrading and then re-upgrade. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-28357) Cannot use Jelly Template after recent 2.40 fix
Title: Message Title Jon Starbird commented on JENKINS-28357 Re: Cannot use Jelly Template after recent 2.40 fix Nope. Downgraded to 2.40 and then upgraded back to 2.40.1 and still can't handle it without the extension being included. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-28357) Cannot use Jelly Template after recent 2.40 fix
Title: Message Title Jon Starbird commented on JENKINS-28357 Re: Cannot use Jelly Template after recent 2.40 fix I will do that right now. Just wanted to add, I have another server that I had NOT updated to 2.40.1, so it's still at 2.40, and on that one I do not have this problem at all. So it does seem to be in 2.40.1. I'll upload the file shortly. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-28357) Cannot use Jelly Template after recent 2.40 fix
Title: Message Title Jon Starbird updated an issue Jenkins / JENKINS-28357 Cannot use Jelly Template after recent 2.40 fix Change By: Jon Starbird Attachment: email-ext.jpi Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-28357) Cannot use Jelly Template after recent 2.40 fix
Title: Message Title Jon Starbird commented on JENKINS-28357 Re: Cannot use Jelly Template after recent 2.40 fix Well I'm on 1.596.2, not sure why that would matter though. Any ideas what could be causing the issue? Fortunately I have a work around now, just putting the extension in, but it would be good for all of us if we found the cause. Anything else I can provide to help? I bumped the Priority down to Major since there is a work around for this. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-28357) Cannot use Jelly Template after recent 2.40 fix
Title: Message Title Jon Starbird updated an issue Jenkins / JENKINS-28357 Cannot use Jelly Template after recent 2.40 fix Change By: Jon Starbird Priority: Blocker Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27728) Windows Batch execution will not work with quoted arguments that have spaces
Jon Starbird edited a comment on JENKINS-27728 Windows Batch execution will not work with quoted arguments that have spaces Incorrectly thought I had a work around but I haven't found one yet. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27728) Windows Batch execution will not work with quoted arguments that have spaces
Jon Starbird commented on JENKINS-27728 Windows Batch execution will not work with quoted arguments that have spaces More info. I tried sticking an Inject Environment variables just before calling the Windows Batch widget and then called the batch script using Jenkins variables, still spaces in everything, but didn't put any quotes anywhere, not when I declared them in Inject Environment Variables and not when I called the script, and this allows it to work. So the bug seems to be in the Windows Batch widget itself. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27728) Windows Batch execution will not work with quoted arguments that have spaces
Jon Starbird commented on JENKINS-27728 Windows Batch execution will not work with quoted arguments that have spaces Daniel, I can run the exact same batch file passing it the same parameters from a CMD window on the same build system and it works with double quotes. In Jenkins when I put in D:\scripts\batch.bat d:\somepath to a file\file.blh d:\someother path\foo.bar and put double quotes around each param, so D:\scripts\batch.bat "d:\somepath to a file\file.blh" "d:\someother path\foo.bar" it will fail. I even tried double quotes around the script itself. Do the same thing in CMD window on the same system, it works. You mentioned Jenkins saves the batch files to a temp file, I did know that but they get deleted to quickly for me to see them. Is there a way to turn off the delete part? Thanks. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27728) Windows Batch execution will not work with quoted arguments that have spaces
Jon Starbird created JENKINS-27728 Windows Batch execution will not work with quoted arguments that have spaces Issue Type: Bug Assignee: Unassigned Components: core Created: 03/Apr/15 12:50 AM Description: I have a batch script that I am passing two full path with filenames arguments to and one of those paths has spaces in it. I have tried double quotes and many other options with the same results of the argument being broken on the spaces by Jenkins. Environment: Jenkins 1.580.3, Windows 7 Pro Project: Jenkins Labels: Windows_Batch Priority: Major Reporter: Jon Starbird This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-24608) Test result link displays twice on matrix project page
Jon Starbird commented on JENKINS-24608 Test result link displays twice on matrix project page Also seeing the same thing, will add that the Trend reports are also Duplicated. Using Publish NUnit. Jenkins 1580.1 and NUnit 0.16. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-26140) Jelly HTML - Modified Template works in Testing mode but fails when build sends email
Jon Starbird created JENKINS-26140 Jelly HTML - Modified Template works in Testing mode but fails when build sends email Issue Type: Bug Assignee: Alex Earl Attachments: html.template.jelly Components: email-ext-plugin Created: 17/Dec/14 5:53 PM Description: Slightly modified the original html.jelly template, I removed the Artifacts portion, and it works fine when running the Test Email Template option. However when run from a build I get the following Exception on any build it is run against, every build does have a Change Set which does appear fine when run in Test mode. I've also attached the Template I am using: Exception raised during template rendering: No such property: changeSet for class: SimpleTemplateScript35 groovy.lang.MissingPropertyException: No such property: changeSet for class: SimpleTemplateScript35 at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:50) at org.codehaus.groovy.runtime.callsite.PogoGetPropertySite.getProperty(PogoGetPropertySite.java:49) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callGroovyObjectGetProperty(AbstractCallSite.java:231) at SimpleTemplateScript35.run(SimpleTemplateScript35.groovy:45) at groovy.text.SimpleTemplateEngine$SimpleTemplate$1.writeTo(SimpleTemplateEngine.java:165) at groovy.text.SimpleTemplateEngine$SimpleTemplate$1.toString(SimpleTemplateEngine.java:177) at hudson.plugins.emailext.plugins.content.ScriptContent.renderTemplate(ScriptContent.java:216) at hudson.plugins.emailext.plugins.content.ScriptContent.evaluate(ScriptContent.java:85) at org.jenkinsci.plugins.tokenmacro.DataBoundTokenMacro.evaluate(DataBoundTokenMacro.java:189) at org.jenkinsci.plugins.tokenmacro.TokenMacro.expand(TokenMacro.java:182) at org.jenkinsci.plugins.tokenmacro.TokenMacro.expandAll(TokenMacro.java:233) at hudson.plugins.emailext.plugins.ContentBuilder.transformText(ContentBuilder.java:72) at hudson.plugins.emailext.ExtendedEmailPublisher.getContent(ExtendedEmailPublisher.java:659) at hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:538) at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:306) at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:297) at hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:244) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) at hudson.model.Build$BuildExecution.cleanUp(Build.java:192) at hudson.model.Run.execute(Run.java:1791) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Environment: Jenkins 1580.1, Plugin 2.39 Project: Jenkins Priority: Major Reporter: Jon Starbird This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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
[JIRA] [email-ext-plugin] (JENKINS-26140) Jelly HTML - Modified Template works in Testing mode but fails when build sends email
Jon Starbird closed JENKINS-26140 as Fixed Jelly HTML - Modified Template works in Testing mode but fails when build sends email No issue. Had forgotten to call script correctly in Email setup, was just using SCRIPT instead of Jelly_Script and just kept over looking it. Change By: Jon Starbird (17/Dec/14 6:58 PM) Status: Open Closed Assignee: AlexEarl JonStarbird Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-25501) Results not being propagated to ENV variables
Jon Starbird commented on JENKINS-25501 Results not being propagated to ENV variables Ok. I didn't know that. However, I put them into the email-ext one and still don't get the correct values. I'll try it again today. I have all plugins you've mentioned and the latest versions, based on the Long-term Support Release of Jenkins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-25501) Results not being propagated to ENV variables
Jon Starbird commented on JENKINS-25501 Results not being propagated to ENV variables No. What I was doing for my testing was using the Tokens Macro values and saving them into Environment variables. But for the emails I was using only the Tokens. I'll try it again this afternoon. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-25501) Results not being propagated to ENV variables
Jon Starbird commented on JENKINS-25501 Results not being propagated to ENV variables Ok it is working in emails now, thanks. Question, what I'm trying to accomplish is I only want my build to Fail or be Unstable with MSBuild warnings but I want the reports for Robocopy and a homemade parser to still be produced. So what I was doing was using the Conditional Multi Step task to run Warnings earlier in the build to get my MSBuild Warnings and then was trying to save those results out and that is where I was trying to put the values saved out as Environment Variables. Is there any way for to get those separate values out?? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-25501) Results not being propagated to ENV variables
Jon Starbird commented on JENKINS-25501 Results not being propagated to ENV variables I tried the ENV method and without it. Neither works. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-25501) Results not being propagated to ENV variables
Jon Starbird
commented on JENKINS-25501
Results not being propagated to ENV variables
You can use Batch or Powershell or pretty much anything that can access Environment variables.
For example if you put his into a Windows batch script and run it you'll get the values for all the WARNINGS variables.
SET WARNINGS
That will list them out in Jenkins console for the build.
Or you can use the Jenkins tokens in a build Email and email them to yourself.
To test I just used both, ${WARNINGS_COUNT} and ${ENV,var="WARNING_COUNT"} with a text tag before each one and then just waited for an email.
Of course you also need something to have Warnings in it.
I used a previous build log that had MSBuild warnings in it. Then set the Warnings scanner to use the file instead of the workspace.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-25501) Results not being propagated to ENV variables
Jon Starbird created JENKINS-25501 Results not being propagated to ENV variables Issue Type: Bug Assignee: Ulli Hafner Components: warnings-plugin Created: 07/Nov/14 10:43 PM Description: variables Warning_Count, Warning_Result and most likely others are not showing correct values. Setup is 3 Warning Parsers, MSBuild, Robocopy, and a custom one. When run many warnings are found in all the types but when trying to use Variables Count always shows 0 and Results always shows Succss Environment: Jenkins 1.580.1, plugin is CI version 4.44 downloaded on 11/5 Project: Jenkins Priority: Major Reporter: Jon Starbird This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mstestrunner] (JENKINS-20366) Results file field doesn't allow a folder to be specified before file name
Jon Starbird commented on JENKINS-20366 Results file field doesnt allow a folder to be specified before file name Yes but it is a very minor issue. I personally like to organize different results to end up with folders like UnitTests, IntegrationTests, Metrics, etc. However the tool is usable without it but having the ability would be nice. If you want to put it off I'd just suggest that making a note in the Tooltip for the field that it can only take a filename and the file has to be in the workspace folder. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings] (JENKINS-22700) Enhance plugin to capture and report errors like it does warnings
Jon Starbird created JENKINS-22700 Enhance plugin to capture and report errors like it does warnings Issue Type: New Feature Affects Versions: current Assignee: Ulli Hafner Components: warnings Created: 21/Apr/14 5:42 PM Description: Add the ability to have Errors reported by the plugin. Having the ability to have the Errors reported like the Warnings would be very useful. Currently some parsers may report errors but they are still listed as Warnings which is confusing to users who view the reports. The simplest solution I think would be to just have users have to make their own parsers and then a flag to indicate if the type the parser is looking for is Warnings or Errors which would then modify the reports to says "Warnings" or "Errors" in all the appropriate places. Environment: Jenkins 1.532.3 Warnings Plugin 4.40 Project: Jenkins Priority: Major Reporter: Jon Starbird This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [vs-code-metrics] (JENKINS-22589) Command line field entries do not undergo variable substitution before metrics program is launched
Jon Starbird created JENKINS-22589 Command line field entries do not undergo variable substitution before metrics program is launched Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: vs-code-metrics Created: 11/Apr/14 9:49 PM Description: If using Jenkins variables in the command line parameters they will not be substituted before run time. Workaround - use Windows command line method of using Environment variables, %varname%, instead of the Jenkins variables. Environment: Jenkins 1.532.2 VS Code Metrics plugin - 1.7 Project: Jenkins Priority: Minor Reporter: Jon Starbird This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [vs-code-metrics] (JENKINS-22541) Cannot use paths with spaces when adding assembly files
Jon Starbird created JENKINS-22541 Cannot use paths with spaces when adding assembly files Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: vs-code-metrics Created: 09/Apr/14 2:06 AM Description: When entering files into the Assembly Files field you cannot include paths with spaces even if you put quotes, single or double, the tool will fail to process the path. Work around is that in the Command Line Arguments you can add /file entries to point to the files that have spaces in their paths putting quotes around each entry. This leaves some confusion when someone else looks at the configuration since the Command Line Arguments is initially hidden under the Advanced area. Be nice if you could enter any kind of path into the Assembly Files section. Environment: Jenkins 1.532.2 and plugin version 1.7 Project: Jenkins Priority: Major Reporter: Jon Starbird This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [vs-code-metrics] (JENKINS-20573) Add flag to set build to Unstable if failure from this plugin
Jon Starbird created JENKINS-20573 Add flag to set build to Unstable if failure from this plugin Issue Type: New Feature Assignee: Unassigned Components: vs-code-metrics Created: 13/Nov/13 11:14 PM Description: Currently if the Metrics tool fails this fails the entire build process. It would be very nice to have the option to not fail it. Environment: Jenkins 1509.4 Project: Jenkins Priority: Major Reporter: Jon Starbird This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [publish-over-cifs] (JENKINS-17885) Publish over SSH lost main configuration data after jenkins server reboot
Jon Starbird commented on JENKINS-17885 Publish over SSH lost main configuration data after jenkins server reboot PLEASE FIX THIS ISSUE. This plugin could be very valuable but with this bug it is completely useless. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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. For more options, visit https://groups.google.com/groups/opt_out.
