[JIRA] (JENKINS-36089) Pipeline support for Promoted Builds Plugin
Title: Message Title steven armstrong commented on JENKINS-36089 Re: Pipeline support for Promoted Builds Plugin To give a use case, we have common ci builds for the following: networking ci build (governs acl rules) load balancing ci build (governs load balancer config) platform image ci build (governs centos/ windows images) developer specific ci build (code compilation). Each of these ci builds have an associated promoted build parameter which when they are successful increments without teams having to manually update dependencies when a check-ins occur to networking, platform or load balancing versions. These ci builds then roll up into a "package build" which generates the build artifact used at deployment time (we build a manifest json file using the artifacts linked to the latest promoted build parameter versions). This is generated every developer check-in and deployment pipelines are then invoked by the new manifest release candidate. This manifest json then consumes the latest networking, load balancing, platform image using promoted build parameters to pull all the necessary artifacts from each ci build and arrange them as the 1st deployment step in the deployment pipeline. Currently not having the promoted build parameter plugin integrated with the pipeline job type means we cant currently make the package build, currently a freestyle job, the 1st step of the jenkinsfile pipeline job and then trigger other jenkinsfile pipeline jobs from it using promotion stars, as it traverses environments. With the promoted build parameter missing from the pipeline job we are missing the ability to: 1) Associate the promoted build parameters with the pipeline job type as part of the jenkinsfile meaning the pipeline jenkinsfile cant be stored in the code repository and used as the trigger event for the quality assurance pipeline. 2) Trigger a pipeline based on a state change to an artifact repository or another build. Currently we use thoughtworks go for pipelines, which allows us to push the manifest file to artifactory and then poll the repository for changes. The urltrigger plugin could provide this feature as well but it also hasnt been converted to the pipeline job type either meaning we currently have no way to trigger pipelines based on an artifact change. An updated promoted build number could be used to act as that trigger rather than the external artifact. 3) We will want to have a jenkinsfile for each pipeline stage so qa, integration, perf and prod by having association between multiple jenkinsfiles is necessary, the promoted build plugin could potentially do this link, so each pipeline promotes a package (promoted build number) that is allowed to be deployed to the next environment by users. This is particularly useful in continuous delivery when in production environments teams can select a promoted build number to deploy the latest build or trigger a previous promoted build number to roll back by selecting it from the dropdown list. The above points are currently blocking us from moving to jenkins 2.x for pipelines from thoughtworks go and probably preventing many others too.
[JIRA] (JENKINS-13043) Test Results Trend graph missing intermittently
[ https://issues.jenkins-ci.org/browse/JENKINS-13043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161040#comment-161040 ] steven armstrong commented on JENKINS-13043: This is a big problem for us as we use jenkins to run lots of aat tests and our dashboard graphs keep dissapearing so the information displayed is not accurate. Any idea what the root cause is and wither this is an easy fix.. > Test Results Trend graph missing intermittently > --- > > Key: JENKINS-13043 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13043 > Project: Jenkins > Issue Type: Bug > Components: nunit >Affects Versions: current > Environment: Windows 2008R2 running Jenkins as a service. This isn't > an error, it's more of a bad state, so there's no stack trace to show. Here's > the /systemInfo dump: > Name Value > awt.toolkit sun.awt.windows.WToolkit > executable-war C:\Apps\Jenkins\jenkins.war > file.encoding Cp1252 > file.encoding.pkg sun.io > file.separator \ > hudson.diyChunking true > hudson.lifecycle hudson.lifecycle.WindowsServiceLifecycle > java.awt.graphicsenv sun.awt.Win32GraphicsEnvironment > java.awt.headless true > java.awt.printerjob sun.awt.windows.WPrinterJob > java.class.path C:\Apps\Jenkins\jenkins.war > java.class.version 50.0 > java.endorsed.dirs C:\Apps\Jenkins\jre\lib\endorsed > java.ext.dirs C:\Apps\Jenkins\jre\lib\ext;C:\Windows\Sun\Java\lib\ext > java.home C:\Apps\Jenkins\jre > java.io.tmpdir C:\Windows\TEMP\ > java.library.path > C:\Apps\Jenkins\jre\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\csvn\bin\;C:\csvn\Python25\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;c:\Program > Files (x86)\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft > SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL > Server\100\DTS\Binn\;c:\Program Files (x86)\Microsoft SQL > Server\100\Tools\Binn\VSShell\Common7\IDE\;c:\Program Files (x86)\Microsoft > SQL Server\100\DTS\Binn\;C:\Program Files\NCover\;C:\Program Files\Microsoft > Windows Performance Toolkit\;c:\Program Files (x86)\Microsoft ASP.NET\ASP.NET > Web Pages\v1.0\;;. > java.runtime.name Java(TM) SE Runtime Environment > java.runtime.version 1.6.0_26-b03 > java.specification.name Java Platform API Specification > java.specification.vendor Sun Microsystems Inc. > java.specification.version 1.6 > java.vendor Sun Microsystems Inc. > java.vendor.url http://java.sun.com/ > java.vendor.url.bug http://java.sun.com/cgi-bin/bugreport.cgi > java.version 1.6.0_26 > java.vm.info mixed mode > java.vm.name Java HotSpot(TM) Client VM > java.vm.specification.name Java Virtual Machine Specification > java.vm.specification.vendor Sun Microsystems Inc. > java.vm.specification.version 1.0 > java.vm.vendor Sun Microsystems Inc. > java.vm.version 20.1-b02 > line.separator > mail.smtp.sendpartial true > mail.smtps.sendpartial true > os.arch x86 > os.name Windows Server 2008 R2 > os.version 6.1 > path.separator ; > sun.arch.data.model 32 > sun.boot.class.path > C:\Apps\Jenkins\jre\lib\resources.jar;C:\Apps\Jenkins\jre\lib\rt.jar;C:\Apps\Jenkins\jre\lib\sunrsasign.jar;C:\Apps\Jenkins\jre\lib\jsse.jar;C:\Apps\Jenkins\jre\lib\jce.jar;C:\Apps\Jenkins\jre\lib\charsets.jar;C:\Apps\Jenkins\jre\lib\modules\jdk.boot.jar;C:\Apps\Jenkins\jre\classes > > sun.boot.library.path C:\Apps\Jenkins\jre\bin > sun.cpu.endian little > sun.cpu.isalist pentium_pro+mmx pentium_pro pentium+mmx pentium i486 i386 i86 > sun.desktop windows > sun.io.unicode.encoding UnicodeLittle > sun.java.command C:\Apps\Jenkins\jenkins.war --httpPort=8080 > sun.java.launcher SUN_STANDARD > sun.jnu.encoding Cp1252 > sun.management.compiler HotSpot Client Compiler > sun.os.patch.level Service Pack 1 > svnkit.http.methods Digest,Basic,NTLM,Negotiate > svnkit.ssh2.persistent false > user.country US > user.dir C:\Windows\system32 > user.home C:\ > user.language en > user.name $ > user.timezone America/Chicago > user.variant > Environment Variables > Name ↓ Value > ALLUSERSPROFILE C:\ProgramData > APPDATA C:\Windows\system32\config\systemprofile\AppData\Roaming > APR_ICONV1_PATH C:\csvn\bin\iconv\ > BASE C:\Apps\Jenkins > COMPUTERNAME 28SVMSVNCI051 > ComSpec C:\Windows\system32\cmd.exe > CommonProgramFiles C:\Program Files (x86)\Common Files > CommonProgramFiles(x86) C:\Program Files (x86)\Common Files > CommonProgramW6432 C:\Program Files\Common Files > FP_NO_HOST_CHECK NO > JAVA_HOME C:\Program Files (x86)\Java\jdk1.6.0_27 > JENKINS_HOME C:\Apps\Jenkins > LOCALAPPDATA C:\Windows\system32\config\systemprofile\AppData\Local > NUMBER_OF_PROCESSORS 2 > OS Windows_NT > PATHEXT .COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WS
[JIRA] (JENKINS-9965) Nunit plugin does not display graph when fingerprinting is used on the xml report
[ https://issues.jenkins-ci.org/browse/JENKINS-9965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161041#comment-161041 ] steven armstrong commented on JENKINS-9965: --- is there any update on this has it been fixed in a later version of jenkins? > Nunit plugin does not display graph when fingerprinting is used on the xml > report > - > > Key: JENKINS-9965 > URL: https://issues.jenkins-ci.org/browse/JENKINS-9965 > Project: Jenkins > Issue Type: Bug > Components: nunit > Environment: XP, all latest software versions as of 6/13/11 >Reporter: mark lemay >Assignee: redsolo > > Nunit plug-in does not display graph when fingerprinting is used on the xml > report -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14730) Support File & Multi Extended Choice parameters
steven armstrong commented on JENKINS-14730 Support File & Multi Extended Choice parameters This would improve the plug-in greatly as it would mean jobs in the plug-in are only run if they meet specific run parameter pre-requisites. It would also mean less nested layers would be required in job configuration. At the moment I have the scenario of using 2 common jobs, a batch job with conditional logic that calls the 2 common jobs and then the multijob plugin that calls the batch which means 3 layers of jobs as opposed to 2 just because the multi-job plug-in doesn't have conditional logic. 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
[JIRA] (JENKINS-14730) Support File & Multi Extended Choice parameters
steven armstrong started work on JENKINS-14730 Support File & Multi Extended Choice parameters Change By: steven armstrong (21/Oct/12 9:45 AM) Status: Open In Progress 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
[JIRA] (JENKINS-14730) Support File & Multi Extended Choice parameters
steven armstrong stopped work on JENKINS-14730 Support File & Multi Extended Choice parameters Change By: steven armstrong (21/Oct/12 9:45 AM) Status: In Progress Open 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
[JIRA] (JENKINS-14730) Support File & Multi Extended Choice parameters
steven armstrong commented on JENKINS-14730 Support File & Multi Extended Choice parameters Does this fix mean we can use the conditional buildstep plugin in a multijob job and not lose the nice job layout on the multijob page? When will this fix go in to a new release of the multijob plugin? 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] (JENKINS-16870) Jenkins cant display multijob view if the multijob face is wrapped in a run condition
steven armstrong created JENKINS-16870 Jenkins cant display multijob view if the multijob face is wrapped in a run condition Issue Type: Bug Affects Versions: current Assignee: domi Components: conditional-buildstep, jenkins-multijob-plugin Created: 19/Feb/13 1:24 AM Description: The conditional buildstep plug-in allows you to specify a multijob phase as build step. However, the graphical display of a multijob phase is lost when a multijob phase is nested in a conditional build step which means it is not very useful as the user can't view it running except in the console log rather than the multijob screen. It would be very helpful to use conditional buildsteps in the multijob plugin and maintain this graphical representation. So could the code be altered so that conditional buildsteps that have a multijob phase as a build step are still displayed by the multijob plugin. Conditional logic is very important when promoting job reuse and not having it means I currently have to have Multijob calling conditional logic job that will run sub-jobs based on the parameters passed by the Multijob. Having conditional logic available to multijob will mean I can have multijob calling jobs directly without the added layer of the conditional job in between and would also allow better visulisation for the end user of all the jobs that are running. Project: Jenkins Priority: Blocker Reporter: steven armstrong 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] (JENKINS-16870) Jenkins cant display multijob view graphically if the multijob phase is wrapped in a conditional buildstep
steven armstrong updated JENKINS-16870 Jenkins cant display multijob view graphically if the multijob phase is wrapped in a conditional buildstep Change By: steven armstrong (19/Feb/13 1:26 AM) Summary: Jenkins cant display multijob view graphically if the multijob face phase is wrapped in a run condition conditional buildstep 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] (JENKINS-14730) Support File & Multi Extended Choice parameters
steven armstrong commented on JENKINS-14730 Support File & Multi Extended Choice parameters Hi Roni, As you say it is possible to: 1) Create a multi-job at the create job page in jenkins 2) As a build step on the multi-job create a conditional buildstep 3) When that conditional buildstep is true run a multijob phase as part of the conditional build step. This executes perfectly command wise having the desired effect from a run perspective. The issue though is that the multi-job phase which is run when the conditional buildstep is true does not show up graphically on the multi-job graphical display, meaning an end user can not see that phase being executed unless you go to the console output. So fixing the plug-in to display phases that are nested in a conditional build-step would greatly benefit end users who wish to see what exactly the multijob plugin is executing at build time without having to drill through to the console log. One of the main benefits the multijob brings is that graphical representation of chained jobs and giving the user the ability to see the plugin step through each job in the phase but that is lost if you call the multijob phase in the conditional build step. Hope that makes sense. The other fix is great though regarding the parameters. However, fixing the view for conditional buildsteps would just make the plugin so much more powerfull. Kind Regards, Steven 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] (JENKINS-14730) Support File & Multi Extended Choice parameters
steven armstrong commented on JENKINS-14730 Support File & Multi Extended Choice parameters No problem, already have raised JENKINS-16870. 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/groups/opt_out.
[JIRA] [parameter-separator] (JENKINS-23530) Ability to Add Text to parameter seperator sections
steven armstrong created JENKINS-23530 Ability to Add Text to parameter seperator sections Issue Type: New Feature Assignee: Unassigned Components: parameter-separator Created: 22/Jun/14 12:52 PM Environment: It would be a nice feature to have the ability to add some text to each parameter separator section which would mean each section could have a section heading. Project: Jenkins Priority: Major Reporter: steven armstrong 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] [parameter-separator] (JENKINS-23530) Ability to Add Text to parameter seperator sections
steven armstrong assigned JENKINS-23530 to Michael Chmielewski Ability to Add Text to parameter seperator sections Change By: steven armstrong (22/Jun/14 12:57 PM) Assignee: Michael Chmielewski 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] [parameter-separator] (JENKINS-23530) Ability to Add Text to parameter seperator sections
steven armstrong commented on JENKINS-23530 Ability to Add Text to parameter seperator sections Thanks for the quick turn around, looks good can we get this added to a 0.6 release. 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] [parameter-separator] (JENKINS-23570) Allow the paremetrised "Build" button to instead say "Deploy" instead of "Build" if the user wishes
steven armstrong created JENKINS-23570 Allow the paremetrised "Build" button to instead say "Deploy" instead of "Build" if the user wishes Issue Type: Improvement Assignee: Unassigned Components: parameter-separator Created: 25/Jun/14 11:02 AM Description: Just want to say thanks so much for this plug-in and the last feature around custom text, it has been so helpful for organizing build parameters to make them readable for end users. This got me thinking as Jenkins is now used for Builds as well as continuous delivery, it would be great if we could toggle the text on the parametrized build button between "Build" and "Deploy" depending on what we are using the build parameters for as lot's of users use them for deployments. It really would be a nice feature and given you have managed to manipulate the build parameters page I thought you may be the person to make it happen. Also it would probably mean this plug-in is used by everyone using Jenkins for continuous delivery which would be a nice bonus. Project: Jenkins Priority: Major Reporter: steven armstrong 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] [parameter-separator] (JENKINS-23570) Allow the paremetrised "Build" button to instead say "Deploy" instead of "Build" if the user wishes
steven armstrong assigned JENKINS-23570 to Michael Chmielewski Allow the paremetrised "Build" button to instead say "Deploy" instead of "Build" if the user wishes Change By: steven armstrong (25/Jun/14 11:03 AM) Assignee: Michael Chmielewski 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] [parameter-separator] (JENKINS-23570) Allow the paremetrised "Build" button to instead say "Deploy" instead of "Build" if the user wishes
steven armstrong commented on JENKINS-23570 Allow the paremetrised "Build" button to instead say "Deploy" instead of "Build" if the user wishes 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] [artifactory] (JENKINS-17967) Generic-Artifactory Integration Resolved Artifacts doesn't attach am artifact dependency in artifactory when using Regex
steven armstrong created JENKINS-17967 Generic-Artifactory Integration Resolved Artifacts doesn't attach am artifact dependency in artifactory when using Regex Issue Type: Bug Affects Versions: current Assignee: yossis Attachments: Jenkins_issue.png, Jenkins_issue2.png, Jenkins_issue3.png Components: artifactory Created: 15/May/13 5:08 PM Description: Hi, When using the Jenkins Artifactory plug-in Generic-Artifactory Integration I have set Resolved Artifacts to: repo_key:Builds/DevOps/DevOps_*/DevOps.zip@DevOps#LATEST as shown in the Jenkins_issue screenshot. This resolves an artifact and downloads it to the Jenkins workspace as expected and shown in Jenkins_Issue2. However for some reason it does not link it in Artifactory as a dependency as shown in Jenkins_Issue3 screenshot. It works as expected using a hard coded path and attaches the artifact dependency to artifactory using: repo_key:Builds/DevOps/DevOps_63/DevOps.zip This is shown in the expected screen shot but I can't hardcore the paths in my build as they continually update and I need to use he latest. If you need any further information please let me know. Thanks. Environment: Windows 2008 R2 Project: Jenkins Priority: Critical Reporter: steven armstrong 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] [artifactory] (JENKINS-17967) Generic-Artifactory Integration Resolved Artifacts doesn't attach an artifact dependency in artifactory when using Regex
steven armstrong updated JENKINS-17967 Generic-Artifactory Integration Resolved Artifacts doesn't attach an artifact dependency in artifactory when using Regex Change By: steven armstrong (15/May/13 5:08 PM) Summary: Generic-Artifactory Integration Resolved Artifacts doesn't attach am an artifact dependency in artifactory when using Regex 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] [jenkinswalldisplay] (JENKINS-17141) Integration with Claim plugin
steven armstrong commented on JENKINS-17141 Integration with Claim plugin Having the name as well as the circle round the job name would be helpful 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] [tfs] (JENKINS-16207) "Changes Summary" diff link broken after migration to TFS 2012
steven armstrong commented on JENKINS-16207 "Changes Summary" diff link broken after migration to TFS 2012 Is this plugin not being worked on anymore? 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] [walldisplay] (JENKINS-18321) When using windows batch command as a build step the wall display doesn't show failed test statistics
steven armstrong created JENKINS-18321 When using windows batch command as a build step the wall display doesn't show failed test statistics Issue Type: Bug Affects Versions: current Assignee: Christian Pelster Components: walldisplay Created: 12/Jun/13 5:18 PM Description: If I use the windows batch command as a build step the test statistics aren't displayed on the wallboard. eg (1/100) so 1 test out of 100 failed. If I remove the windows batch command as a build step the statistics are shown. No other build steps cause this issue. I am using the mstest trx plugin to display the tests. I am using Tomcat 7 on windows 2008 R2 Environment: Windows 2008 R2 Project: Jenkins Priority: Major Reporter: steven armstrong 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] [jenkinswalldisplay] (JENKINS-18321) When using windows batch command as a build step the wall display doesn't show failed test statistics
steven armstrong updated JENKINS-18321 When using windows batch command as a build step the wall display doesn't show failed test statistics Change By: steven armstrong (12/Jun/13 5:21 PM) Component/s: jenkinswalldisplay Component/s: walldisplay 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] [jenkins-multijob-plugin] (JENKINS-18307) Multijob "Schedule a Build" Button in the Multijob view stopped working
steven armstrong commented on JENKINS-18307 Multijob "Schedule a Build" Button in the Multijob view stopped working Another issue in the new version is that the main console log next to the schedule build button displays a broken link if it is accessed via the dashboard view or any other custom view and not from the all view. 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] [jenkins-multijob-plugin] (JENKINS-19524) start multijob from any phase
steven armstrong commented on JENKINS-19524 start multijob from any phase This would be a great feature it would have to have the ability to pass the parent multijobs build parameters to the downstream job when starting a child downstream job in isolation. 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] [rebuild] (JENKINS-20596) Support rebuilding jobs using promoted builds parameter
steven armstrong commented on JENKINS-20596 Support rebuilding jobs using promoted builds parameter When will this be in the new release really need it... 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] [tfs] (JENKINS-21120) TFS Service is now shown as the submitter of all gated check-ins as opposed to proper user
steven armstrong created JENKINS-21120 TFS Service is now shown as the submitter of all gated check-ins as opposed to proper user Issue Type: Bug Assignee: redsolo Components: tfs Created: 22/Dec/13 1:15 AM Description: TFS Service is now shown as the submitter of all check-ins as opposed to the person who submitted the change-set through the gates. This means that culprits and points assigned leader board are inaccurate if someone breaks the build. This has been introduced in version 3.0 of the plug-in but worked fine in earlier versions. Environment: windows 2008 r2 Project: Jenkins Priority: Major Reporter: steven armstrong 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] [tfs] (JENKINS-21120) TFS Service is now shown as the submitter of all gated check-ins as opposed to proper user
steven armstrong assigned JENKINS-21120 to steven armstrong TFS Service is now shown as the submitter of all gated check-ins as opposed to proper user Change By: steven armstrong (22/Dec/13 1:18 AM) Assignee: redsolo steven armstrong 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] [tfs] (JENKINS-21120) TFS Service is now shown as the submitter of all gated check-ins as opposed to proper user
steven armstrong updated JENKINS-21120 TFS Service is now shown as the submitter of all gated check-ins as opposed to proper user Change By: steven armstrong (22/Dec/13 1:19 AM) Assignee: steven armstrong 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] [tfs] (JENKINS-21120) TFS Service is now shown as the submitter of all gated check-ins as opposed to proper user
steven armstrong updated JENKINS-21120 TFS Service is now shown as the submitter of all gated check-ins as opposed to proper user Change By: steven armstrong (22/Dec/13 1:22 AM) Assignee: Olivier Dagenais 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] [jenkins-multijob-plugin] (JENKINS-21616) multiconfiguration job when added to a multijob phase doesn't show as executing in multijob graphical view
steven armstrong created JENKINS-21616 multiconfiguration job when added to a multijob phase doesn't show as executing in multijob graphical view Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: jenkins-multijob-plugin Created: 02/Feb/14 4:31 PM Description: When adding a multi-configuration job to a multijob phase, the multi-configuration job shows correctly in the multijob graphical view. However, upon building the multijob it will functionally execute multi-configuration job as desired which is confirmed if you look at the main multijobs main console output, but it doesn't generate a console log or appear in the multijobs main graphical view so it looks like it has actually failed to initiate the phase containing the multi-configuration job. Could this be fixed to show the multi-configration job as executing and generate a console log and timings like free-style jobs do in the multijob graphical view? Environment: Windows 2008 R2 Project: Jenkins Priority: Major Reporter: steven armstrong 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] [jenkins-multijob-plugin] (JENKINS-22416) Add ParameterFactories option to Multijob Build Step
steven armstrong created JENKINS-22416 Add ParameterFactories option to Multijob Build Step Issue Type: New Feature Assignee: Dominik Bartholdi Attachments: ParameterFactories.jpg Components: jenkins-multijob-plugin, nodelabelparameter Created: 29/Mar/14 1:07 PM Description: The multijob plugin currently allows Parameters to be added on each multijob step where you can assign a nodelabel to restrict it to run on a particular slave, It doesn't have the ParameterFactories option though. I have the need to assign a multijob build step to run concurrently on multiple nodes, the multijob step is essentially doing the same task as the "Trigger/call builds on other projects" build step which has the ParameterFactories option. The ParameterFactories option allows this factory to trigger a build of a specific project on all nodes having the same label. It would be of massive help to have this ParameterFactories available on a multijob build step. Environment: All Project: Jenkins Priority: Major Reporter: steven armstrong 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] [promoted-builds-plugin] (JENKINS-25011) Promoted Builds does not work with CloudBees Folder plugin
steven armstrong commented on JENKINS-25011 Promoted Builds does not work with CloudBees Folder plugin The promotion build parameter also does not work 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] [build-flow-plugin] (JENKINS-25909) Allow support for Build Flow Plugin job type for environment dashboard plugin
steven armstrong created JENKINS-25909 Allow support for Build Flow Plugin job type for environment dashboard plugin Issue Type: Improvement Assignee: Nicolas De Loof Components: build-flow-plugin Created: 04/Dec/14 10:58 AM Description: Currently there is no option to enable the environment dashboard plugin to work with the Jenkins Build Flow plugin job type, it would be good if this could be introduced as a lot of pipeline jobs are wrapped in the dsl. Also the environment-dashboard plugin does not have a Component options to associate this Jira ticket against with so this will need created so we can assign tickets properly for this new plugin. At the moment i have assigned it to build-flow-plugin only Thanks. Project: Jenkins Priority: Major Reporter: steven armstrong 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.
