[JIRA] [cucumber-testresult-plugin] (JENKINS-32994) Mark build with failed test as unstable instead of failed
Title: Message Title
John Cunliffe commented on JENKINS-32994
Re: Mark build with failed test as unstable instead of failed
it is quite possible, that I am using it wrongly, however I can not yet see how. please find the troublesome console output below:
Unable to find source-code formatter for language: bash. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml
Updating selenium standalone
downloading https://selenium-release.storage.googleapis.com/2.51/selenium-server-standalone-2.51.0.jar...
Updating chromedriver
downloading https://chromedriver.storage.googleapis.com/2.21/chromedriver_linux64.zip...
chromedriver_2.21.zip downloaded to /home/portos/workspace/front.berater-build-playground/com.dvag.portos.front.berater/node_modules/protractor/selenium/chromedriver_2.21.zip
selenium-server-standalone-2.51.0.jar downloaded to /home/portos/workspace/front.berater-build-playground/com.dvag.portos.front.berater/node_modules/protractor/selenium/selenium-server-standalone-2.51.0.jar
[18:45:41] Server started http://localhost:
Starting selenium standalone server...
[launcher] Running 1 instances of WebDriver
Selenium standalone server started at http://10.61.9.140:34994/wd/hub
Funktionalität: B01 Mein Vermögensberater
Es soll ein Bereich "Mein Vermögensberater" existieren, in dem die Daten des Vermögensberaters (VB) angezeigt werden.
[36m@Abnahme [39m
Szenariogrundriss: Beispiel anzeigen
[32mAngenommen ich befinde mich auf Beispielseite mit der ID "8152200" [39m
[31mDann wird "Max" im Feld "Vorname" des Beispiels angezeigt [39m
AssertionError: expected '' to equal 'Max'
[36mDann wird "Mustermann" im Feld "Name" des Beispiels angezeigt [39m
Failing scenarios:
features/BeraterKomplett.feature:36 # Scenario: Berater in der Komplettansicht anzeigen
1 scenario ( [31m1 failed [39m)
3 steps ( [31m1 failed [39m, [36m1 skipped [39m, [32m1 passed [39m)
0m02.210s
Shutting down selenium standalone server.
[launcher] 0 instance(s) of WebDriver still running
[launcher] phantomjs #1 failed 1 test(s)
[launcher] overall: 1 failed spec(s)
[launcher] Process exited with error code 1
[18:45:54] Finished 'protractor.start' after 15 s
[18:45:54] Starting 'build.docs'...
[18:45:55] Server stopped
(...)
[Cucumber Tests] Parsing results.
[Cucumber Tests] parsing cucumber-abnahme.json
Build step 'Publish Cucumber test result report' changed build result to FAILURE
Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered
Finished: FAILURE
This generates the json displayed below:
[
{
"id": "B01-Mein-Beispiel",
"name": "B01 Mein Beispiel",
"description": "Es soll ein Bereich \"Mein Beispiel\" existieren.",
"line": 3,
"keyword": "Funktionalität",
"uri": "/home/test/workspace/playground/features/MeinBeispiel.feature",
"elements": [
{
"name": "Ich bin als Kunde angemeldet.",
"keyword": "Grundlage",
"description": "",
"type": "background",
"line": 6
},
{
"name": "Beispiel anzeigen",
"id": "B01-Mein-Beispiel;beispiel-anzeigen",
"line": 36,
"keyword": "Scenario",
"description": "
[JIRA] [jira-trigger-plugin] (JENKINS-33012) Notification on Jenkins build activity
Title: Message Title Wisen Tanasa created an issue Jenkins / JENKINS-33012 Notification on Jenkins build activity Issue Type: Improvement Assignee: Wisen Tanasa Components: jira-trigger-plugin Created: 18/Feb/16 8:42 AM Priority: Major Reporter: Wisen Tanasa As a Jenkins user, I would like to be notified if there's an attempt from a user to trigger a build but the build is not triggered so that I would be able to know if I have configured the job correctly. Scenario: User add a comment that matches a job's comment pattern, but the build is not triggered due to wrongly configured JQL filter. As a user, I would like to get a notification when the build that has been triggered by me has failed, so that I can contact my Jenkins administrator without waiting indefinitely. JIRA Webhooks are sending User shape at the moment that is not processed by JIRA Trigger Plugin: User shape contains the user email address that can be freely used in Jenkins build step to send email. User shape contains the username that can be used for adding a JIRA comment with the user tagged e.g. by using JIRA Issue Updater Plugin.
[JIRA] [jira-trigger-plugin] (JENKINS-33012) Notification on Jenkins build activity
Title: Message Title Wisen Tanasa updated an issue Jenkins / JENKINS-33012 Notification on Jenkins build activity Change By: Wisen Tanasa As a Jenkins user, I would like to be notified if there's an attempt from a user to trigger a build but the build is not triggered so that I would be able to know if I have configured the job correctly. Scenario: User add a comment that matches a job's comment pattern, but the build is not triggered due to wrongly configured JQL filter.As a user, I would like to get a notification when the build that has been triggered by me has failed, so that I can contact my Jenkins administrator without waiting indefinitely.JIRA Webhooks are sending User shape at the moment that is not processed by JIRA Trigger Plugin . If this information is parsed and injected via Jenkins environment variables, the following actions can then be done in Jenkins :* User shape contains the user email address that can be freely used in Jenkins build step to send email.* User shape contains the username that can be used for adding a JIRA comment with the user tagged e.g. by using JIRA Issue Updater Plugin. 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-13768) default parameter values are ignored when triggering parameterized build from groovy post-build script
Title: Message Title Night Wolf commented on JENKINS-13768 Re: default parameter values are ignored when triggering parameterized build from groovy post-build script +1 Larry Archer this is a big problem 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-33011) exit -1073741819 Jenkins issue
Title: Message Title Jyothi Bosle started work on JENKINS-33011 Change By: Jyothi Bosle Status: Open In Progress 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-33011) exit -1073741819 Jenkins issue
Title: Message Title Jyothi Bosle updated an issue Jenkins / JENKINS-33011 exit -1073741819 Jenkins issue Change By: Jyothi Bosle Hi, I am using Jenkins for Siebel Automation. I have created a Jenkins job (Execute windows batch command) and trying to run it on the slave. It worked well for the first time. But later on,It is giving the below error C:\Jenkins\workspace\test>exit -1073741819PFB the console output of the build Started by user Jyothi Bosle Building remotely on wsweb0674 in workspace C:/Jenkins/workspace/test [test] $ cmd /c call E:\Apps\Temp\hudson1511287041172085521.bat C:\Jenkins\workspace\test>E:\Siebel\8.1\Tools_2\BIN\siebdev.exe /c E:\Siebel\8.1\Tools_2\bin\enu\tools.cfg /d ServerDataSrc /u sadmin /p teldev2m1n /bc "Siebel Repository" "E:\JenkinsScripts\FC_SRF\siebel_sia.srf" C:\Jenkins\workspace\test>exit -1073741819 Build step 'Execute Windows batch command' marked build as failure [BFA] Scanning build for known causes... [BFA] No failure causes found [BFA] Done. 0s Finished: FAILURE unable to find much information on Google. 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] [cucumber-testresult-plugin] (JENKINS-32994) Mark build with failed test as unstable instead of failed
Title: Message Title James Nord commented on JENKINS-32994 Re: Mark build with failed test as unstable instead of failed Right so in this case every single feature in every single scenario failed. As this is highly unusual[1] (you would expect at least one scenario to pass) the plugin treats this as a failure. Of you have st least one passing scenario then faiures would mark the build as unstable. [1] something like the SUT is not alive. 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-32910) Jelly file was not found after update
Title: Message Title Alex Earl resolved as Fixed Fixed class loader to previous behavior. Released as 2.41.2 Jenkins / JENKINS-32910 Jelly file was not found after update Change By: Alex Earl Status: Open Resolved Resolution: Fixed 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-32889) Configurable delimiter
Title: Message Title Alex Earl resolved as Fixed Fixed in 2.41.2 Jenkins / JENKINS-32889 Configurable delimiter Change By: Alex Earl Status: In Progress Resolved Resolution: Fixed 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] [cucumber-testresult-plugin] (JENKINS-32994) Mark build with failed test as unstable instead of failed
Title: Message Title John Cunliffe commented on JENKINS-32994 Re: Mark build with failed test as unstable instead of failed This makes sense - I will double check and assuming that a single passing test will result in an unstable status, my problems will be solved. 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] [jabber-plugin] (JENKINS-31941) Got a 503/cancel when Jenkins sends a message to Google Hangout
Title: Message Title Edward Quick commented on JENKINS-31941 Re: Got a 503/cancel when Jenkins sends a message to Google Hangout I have the same issue, and can't get notifications to work with Jabber. Feb 18, 2016 10:28:59 AM INFO hudson.plugins.jabber.im.transport.JabberIMConnection connect Connected to XMPP on null:0/gmail.com using secure connection Feb 18, 2016 10:28:59 AM FINE hudson.plugins.jabber.im.transport.JabberConnectionDebugger SENT: quick Feb 18, 2016 10:29:23 AM FINE hudson.plugins.jabber.im.transport.JabberConnectionDebugger SENT: Project gameoflife-default build #15: STILL UNSTABLE in 47 sec: http://localhost:8080/job/gameoflife-default/15/c5107486-f574-450f-9dca-a11abf295bfa Feb 18, 2016 10:29:23 AM FINE hudson.plugins.jabber.im.transport.JabberConnectionDebugger RECV: Project gameoflife-default build #15: STILL UNSTABLE in 47 sec: http://localhost:8080/job/gameoflife-default/15/c5107486-f574-450f-9dca-a11abf295bfa Feb 18, 2016 10:29:23 AM FINEST hudson.plugins.jabber.im.transport.JabberConnectionDebugger RCV PKT: Project gameoflife-default build #15: STILL UNSTABLE in 47 sec: http://localhost:8080/job/gameoflife-default/15/c5107486-f574-450f-9dca-a11abf295bfa Feb 18, 2016 10:29:23 AM FINE hudson.plugins.jabber.im.transport.JabberConnectionDebugger RECV: Feb 18, 2016 10:31:36 AM FINE hudson.plugins.jabber.im.transport.JabberConnectionDebugger RECV: 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] [ssh-credentials-plugin] (JENKINS-26379) Jenkins - ssh connection exception
Title: Message Title Lieven Cardoen commented on JENKINS-26379 Re: Jenkins - ssh connection exception My logs after restart of my Jenkins master VM (deleting all logs before starting Jenkins again). feb 18, 2016 12:06:36 PM winstone.Logger logInternal INFO: Beginning extraction from war file feb 18, 2016 12:06:36 PM org.eclipse.jetty.util.log.JavaUtilLog info INFO: jetty-winstone-2.9 feb 18, 2016 12:06:40 PM org.eclipse.jetty.util.log.JavaUtilLog info INFO: NO JSP Support for , did not find org.apache.jasper.servlet.JspServlet feb 18, 2016 12:06:41 PM org.eclipse.jetty.util.log.JavaUtilLog info INFO: Started SelectChannelConnector@0.0.0.0:8080 feb 18, 2016 12:06:41 PM winstone.Logger logInternal INFO: Winstone Servlet Engine v2.0 running: controlPort=disabled feb 18, 2016 12:06:42 PM jenkins.InitReactorRunner$1 onAttained INFO: Started initialization feb 18, 2016 12:06:42 PM jenkins.InitReactorRunner$1 onAttained INFO: Listed all plugins Feb 18, 2016 12:06:43 PM jenkins.InitReactorRunner$1 onAttained INFO: Prepared all plugins Feb 18, 2016 12:06:56 PM jenkins.InitReactorRunner$1 onAttained INFO: Started all plugins Feb 18, 2016 12:06:56 PM jenkins.InitReactorRunner$1 onAttained INFO: Augmented all extensions Feb 18, 2016 12:06:56 PM hudson.slaves.SlaveComputer tryReconnect INFO: Attempting to reconnect DEV-G-UX Feb 18, 2016 12:06:56 PM hudson.slaves.SlaveComputer tryReconnect INFO: Attempting to reconnect SRV-CI-MADE-UNIX Feb 18, 2016 12:07:01 PM jenkins.InitReactorRunner$1 onAttained INFO: Loaded all jobs Feb 18, 2016 12:07:02 PM hudson.model.AsyncPeriodicWork$1 run INFO: Started Download metadata Feb 18, 2016 12:07:02 PM hudson.model.AsyncPeriodicWork$1 run INFO: Finished Download metadata. 3 ms Feb 18, 2016 12:07:04 PM org.springframework.context.support.AbstractApplicationContext prepareRefresh INFO: Refreshing org.springframework.web.context.support.StaticWebApplicationContext@2e6b353e: display name [Root WebApplicationContext]; startup date [Thu Feb 18 12:07:04 CET 2016]; root of context hierarchy Feb 18, 2016 12:07:04 PM org.springframework.context.support.AbstractApplicationContext obtainFreshBeanFactory INFO: Bean factory for application context [org.springframework.web.context.support.StaticWebApplicationContext@2e6b353e]: org.springframework.beans.factory.support.DefaultListableBeanFactory@646d5af4 Feb 18, 2016 12:07:04 PM org.springframework.beans.factory.support.DefaultListableBeanFactory preInstantiateSingletons INFO: Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@646d5af4: defining beans [authenticationManager]; root of factory hierarchy Feb 18, 2016 12:07:04 PM org.springframework.context.support.AbstractApplicationContext prepareRefresh INFO: Refreshing org.springframework.web.context.support.StaticWebApplicationContext@196a1c5d: display name [Root WebApplicationContext]; startup date [Thu Feb 18 12:07:04 CET 2016]; root of context hierarchy Feb 18, 2016 12:07:04 PM org.springframework.context.support.AbstractApplicationContext obtainFreshBeanFactory INFO: Bean factory for application context [org.springframework.web.context.support.StaticWebApplicationContext@196a1c5d]: org.springframework.beans.factory.support.DefaultListableBeanFactory@508b1fd3 Feb 18, 2016 12:07:04 PM org.springframework.beans.factory.support.DefaultListableBeanFactory preInstantiateSingletons INFO: Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@508b1fd3: defining beans [filter,legacy]; root of factory hierarchy Feb 18, 2016 12:07:04 PM org.jenkinsci.main.modules.sshd.SSHD start INFO: Started SSHD at port 49503 Feb 18, 2016 12:07:04 PM jenkins.InitReactorRunner$1 onAttained INFO: Completed initialization Feb 18, 2016 12:07:04 PM hudson
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-33013) Unable to execute test in HP Performance Center 12
Title: Message Title Jayashree Purushothaman created an issue Jenkins / JENKINS-33013 Unable to execute test in HP Performance Center 12 Issue Type: Bug Assignee: Ofir Shaked Components: hp-application-automation-tools-plugin Created: 18/Feb/16 11:14 AM Priority: Blocker Reporter: Jayashree Purushothaman When the project is build, Performance center gets connected and logged in. However after sending run request, the test doesn't get started and logs out immediately. Please find the console output below: Started by user anonymous Building in workspace C:\Program Files\Jenkins\workspace\PMC_eCommerce_LoadTest - - Test description: PC 12.0 Validating parameters before run Trying to login [PCServer='almrwc605p-pcs.saas.hp.com', User='pt_vpuruja'] Login succeeded Sending run request [Domain='DEFAULT_Pearson', Project='pt_451', TestID='4399', TestInstanceID='1250', TimeslotDuration='0:30(h:mm)', PostRunAction='Collate And Analyze'] Logout succeeded Empty Results Result Status: UNSTABLE - - Build step 'Execute HP tests using HP Performance Center' changed build result to UNSTABLE Report not found Build step 'Publish HP tests result' changed build result to FAILURE Finished: FAILURE
[JIRA] [mercurial-plugin] (JENKINS-7600) Add support for building a specific changeset
Title: Message Title Sylvain Thénault commented on JENKINS-7600 Re: Add support for building a specific changeset We've similar needs : due to our development workflow using mercurial we may push several heads at once (or during a period of time lower than time needed for a test job) but we want jenkins to start test on every heads. I've made a pull request some time ago allowing this but it has not been integrated and any feedback or help to get it in would be welcome: https://github.com/jenkinsci/mercurial-plugin/pull/72 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] [ssh-credentials-plugin] (JENKINS-26379) Jenkins - ssh connection exception
Title: Message Title Lieven Cardoen commented on JENKINS-26379 Re: Jenkins - ssh connection exception Installing the Java Cryptography Extension (JCE) unlimited strength jurisdiction policy files doesn't resolve the issue. Kind regards, Lieven Cardoen 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] [ssh-credentials-plugin] (JENKINS-26379) Jenkins - ssh connection exception
Title: Message Title Lieven Cardoen commented on JENKINS-26379 Re: Jenkins - ssh connection exception Also doesn't work with root user. Kind regards, Lieven Cardoen 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] [ssh-credentials-plugin] (JENKINS-26379) Jenkins - ssh connection exception
Title: Message Title Lieven Cardoen commented on JENKINS-26379 Re: Jenkins - ssh connection exception Using port 443 instead of port 22 also doesn't work. (suggested by someone on Stackoverflow). http://stackoverflow.com/questions/27226845/unable-to-start-slave-node-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] [maven-plugin] (JENKINS-4428) MavenProbeAction exposes password parameters
Title: Message Title Anders Hammar commented on JENKINS-4428 Re: MavenProbeAction exposes password parameters Ping. Could someone review and merge please? 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] [p4-plugin] (JENKINS-30622) Add View Mask Polling Filter
Title: Message Title Bruce Heather commented on JENKINS-30622 Re: Add View Mask Polling Filter It would also be useful to be able to only sync the files that match the view mask as implemented in the cummunity authored plugin 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] [copy-to-slave-plugin] (JENKINS-28572) copy-to-slave-plugin unable to copy directories
Title: Message Title James Housley commented on JENKINS-28572 Re: copy-to-slave-plugin unable to copy directories This works fine for me using either */ or [Folder name]/*/ 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] [parameterized-remote-trigger-plugin] (JENKINS-32671) Unable to trigger remote builds without parameters
Title: Message Title Alin Stelian commented on JENKINS-32671 Re: Unable to trigger remote builds without parameters Hi guys, same problem here, I have the latest Jenkins version (1.647). Is very annoying when something like this happens, so my question for you is, do you have any workaround 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] [workflow-plugin] (JENKINS-33008) Rename or alias `node` keyword to `agent`
Title: Message Title Jesse Glick resolved as Won't Do AFAIK node is still in use to mean master or agent. Jenkins / JENKINS-33008 Rename or alias `node` keyword to `agent` Change By: Jesse Glick Status: Open Resolved Resolution: Won't Do 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] [workflow-plugin] (JENKINS-32997) Pipeline job: Abort older builds which are running
Title: Message Title Jesse Glick resolved as Incomplete Might be possible already, might not. There is no sample script, and no clear definition of the problem or criteria for a solution. Open-ended questions like this are probably best sent to Stack Overflow rather than the bug tracker, which is intended for clear, concrete fix or enhancement requests. Jenkins / JENKINS-32997 Pipeline job: Abort older builds which are running Change By: Jesse Glick Status: Open Resolved Resolution: Incomplete 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] [workflow-plugin] (JENKINS-33005) Hang in StageStepExecution.println
Title: Message Title Jesse Glick started work on JENKINS-33005 Change By: Jesse Glick Status: Open In Progress 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] [workflow-plugin] (JENKINS-32948) ["git" step] Add "WipeWorkspace" option to simplify release jobs
Title: Message Title Jesse Glick resolved as Won't Do I do no plan to add any more options to the git step. checkout should be used. Jenkins / JENKINS-32948 ["git" step] Add "WipeWorkspace" option to simplify release jobs Change By: Jesse Glick Status: Open Resolved Resolution: Won't Do 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] [workflow-plugin] (JENKINS-32925) StackOverflow when trying to get Pipeline GDSL file
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-32925 StackOverflow when trying to get Pipeline GDSL file Change By: Jesse Glick Labels: pipeline workflow 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] [workflow-plugin] (JENKINS-32925) StackOverflow when trying to get Pipeline GDSL file
Title: Message Title Jesse Glick commented on JENKINS-32925 Re: StackOverflow when trying to get Pipeline GDSL file Some particular plugin triggers the bug. Multiple SCMs is known 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] [workflow-plugin] (JENKINS-32925) StackOverflow when trying to get Pipeline GDSL file
Title: Message Title Jesse Glick assigned an issue to Kristin Whetstone Jenkins / JENKINS-32925 StackOverflow when trying to get Pipeline GDSL file Change By: Jesse Glick Assignee: Jesse Glick Kristin Whetstone 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] [workflow-plugin] (JENKINS-32902) Multibranch pipeline has issues with / in jobName
Title: Message Title Jesse Glick resolved as Not A Defect A bug in your Maven plugin, unit test, etc., not in Jenkins. A typical mistake would be using File.toURL, which is known to be broken (use toURI instead, or toPath() if you can assume Java 7+). Jenkins / JENKINS-32902 Multibranch pipeline has issues with / in jobName Change By: Jesse Glick Status: Open Resolved Resolution: Not A Defect 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] [workflow-plugin] (JENKINS-32863) Sleep function causes premature exit of loop in some cases
Title: Message Title Jesse Glick resolved as Not A Defect You may not use Pipeline steps inside a @NonCPS method. Jenkins / JENKINS-32863 Sleep function causes premature exit of loop in some cases Change By: Jesse Glick Status: Open Resolved Resolution: Not A Defect 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] [workflow-plugin] (JENKINS-32829) Pre-empted builds not stopped in stage with concurrency:1
Title: Message Title Jesse Glick commented on JENKINS-32829 Re: Pre-empted builds not stopped in stage with concurrency:1 The current behavior is as designed. Older builds are canceled if there is a newer build waiting to enter the stage. In other words, if build 1 is in the stage, 2 is waiting to enter, and 3 gets to the same stage statement, 2 will be canceled. If builds reach the stage statement out of order, so build 1 takes a long time to get through earlier stages, and then build 2 enters the stage, 1 will wait for it to exit the stage and then proceed. I think what you are looking for is the linear option suggested in JENKINS-27039. I will not mark this a duplicate since the main planned fix there is the eager option, which is for a different purpose. 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] [workflow-plugin] (JENKINS-32829) Older builds allowed to wait for a throttled stage which a newer build is in
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-32829 Older builds allowed to wait for a throttled stage which a newer build is in Change By: Jesse Glick Summary: Pre-empted Older builds not stopped in allowed to wait for a throttled stage with concurrency:1 which a newer build is in 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] [workflow-plugin] (JENKINS-32783) Deleting a Pipeline project does not stop its running build
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-32783 Deleting a Pipeline project does not stop its running build Probably not specific to multibranch. Change By: Jesse Glick Summary: Removing Deleting a Multibranch Pipeline project does not stop its running build 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] [workflow-plugin] (JENKINS-32925) StackOverflow when trying to get Pipeline GDSL file
Title: Message Title Nickolay Rumyantsev commented on JENKINS-32925 Re: StackOverflow when trying to get Pipeline GDSL file This is my testing instance, it has a hundred of plugins installed for evaluation purposes. I can provide you a list but it should take pretty much time to check them all 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] [workflow-plugin] (JENKINS-32782) Unable to delete unconfigured multibranch pipeline
Title: Message Title Jesse Glick commented on JENKINS-32782 Re: Unable to delete unconfigured multibranch pipeline Also the Edit View link is present, but a 404. 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] [remoting] (JENKINS-32980) Make it easier to use JNLP slaves with self-signed TLS certificates on Jenkins
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32980 Re: Make it easier to use JNLP slaves with self-signed TLS certificates on Jenkins Code changed in jenkins User: Oleg Nenashev Path: src/main/java/hudson/remoting/Engine.java src/main/java/hudson/remoting/jnlp/Main.java http://jenkins-ci.org/commit/remoting/93c42ab4370b06f6d8b205e9a0a2c359f3d65708 Log: Merge pull request #72 from jenkinsci/jenkins-32980 [FIXED JENKINS-32980] Adds a new CLI option to specify additional X.509 certs Compare: https://github.com/jenkinsci/remoting/compare/7a50b43850b1...93c42ab4370b 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] [workflow-plugin] (JENKINS-32782) Unable to delete unconfigured multibranch pipeline
Title: Message Title Jesse Glick commented on JENKINS-32782 Re: Unable to delete unconfigured multibranch pipeline Not quite sure where the problem lies, but probably a regression from JENKINS-31381 : the welcome view is either missing some require sidepanel include, or some existing sidepanel include is misbehaving. 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] [branch-api-plugin] (JENKINS-32782) Unable to delete unconfigured multibranch pipeline
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-32782 Unable to delete unconfigured multibranch pipeline Workaround is to append delete to the multibranch project page and confirm—basically browse to the URL the sidepanel would have linked to. Change By: Jesse Glick Component/s: branch-api-plugin Component/s: workflow-plugin Labels: workflow 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,
[JIRA] [branch-api-plugin] (JENKINS-33006) "Periodically if not otherwise run" interval value acts erratically
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-33006 "Periodically if not otherwise run" interval value acts erratically Change By: Jesse Glick Labels: folders multibranch pipeline workflow 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] [workflow-plugin] (JENKINS-33008) Rename or alias `node` keyword to `agent`
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-33008 Rename or alias `node` keyword to `agent` Change By: Jesse Glick Labels: 2.0 pipeline 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] [mstest-plugin] (JENKINS-32937) Request to make MSTest Plugin compatible with the new workflow
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-32937 Request to make MSTest Plugin compatible with the new workflow Change By: Jesse Glick Labels: pipeline workflow 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-32867) Make build-name-setter-plugin compatible with Pipeline
Title: Message Title Jesse Glick resolved as Won't Fix Jenkins / JENKINS-32867 Make build-name-setter-plugin compatible with Pipeline Change By: Jesse Glick Status: Open Resolved Resolution: Won't Fix 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] [log-parser-plugin] (JENKINS-32866) Log Parser Plugin does not parse Pipeline console outputs
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-32866 Log Parser Plugin does not parse Pipeline console outputs Change By: Jesse Glick Labels: pipeline workflow 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-32867) Make build-name-setter-plugin compatible with Pipeline
Title: Message Title Jesse Glick commented on JENKINS-32867 Re: Make build-name-setter-plugin compatible with Pipeline Use displayName rather than description. 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-32867) Make build-name-setter-plugin compatible with Pipeline
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-32867 Make build-name-setter-plugin compatible with Pipeline Change By: Jesse Glick Labels: pipeline workflow 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] [p4-plugin] (JENKINS-32616) Add support for multibranch pipelines
Title: Message Title Jesse Glick commented on JENKINS-32616 Re: Add support for multibranch pipelines Meaning, an SCMSource implementation. 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] [ghprb-plugin] (JENKINS-32556) Workflow plugin now Pipeline crashes with GitHub Pull Request Builder plugin
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-32556 Workflow plugin now Pipeline crashes with GitHub Pull Request Builder plugin Change By: Jesse Glick Labels: ghprb pipeline workflow 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] [p4-plugin] (JENKINS-32616) Add support for multibranch pipelines
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-32616 Add support for multibranch pipelines Change By: Jesse Glick Labels: multibranch p4 pipeline workflow 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] [ghprb-plugin] (JENKINS-32556) Workflow plugin now Pipeline crashes with GitHub Pull Request Builder plugin
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-32556 Workflow plugin now Pipeline crashes with GitHub Pull Request Builder plugin Change By: Jesse Glick Component/s: ghprb-plugin 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] [ghprb-plugin] (JENKINS-32556) Workflow plugin now Pipeline crashes with GitHub Pull Request Builder plugin
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-32556 Workflow plugin now Pipeline crashes with GitHub Pull Request Builder plugin Change By: Jesse Glick Component/s: ghprb-plugin Component/s: workflow-plugin 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] [ghprb-plugin] (JENKINS-32556) Workflow plugin now Pipeline crashes with GitHub Pull Request Builder plugin
Title: Message Title Jesse Glick commented on JENKINS-32556 Re: Workflow plugin now Pipeline crashes with GitHub Pull Request Builder plugin You can instead create a multibranch pipeline using the GitHub branch source, which as soon as JENKINS-32749 is implemented will support pull requests as well. 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] [ghprb-plugin] (JENKINS-32556) Workflow plugin now Pipeline crashes with GitHub Pull Request Builder plugin
Title: Message Title Jesse Glick commented on JENKINS-32556 Re: Workflow plugin now Pipeline crashes with GitHub Pull Request Builder plugin Whether or not the feature request is accepted, this code is an obvious bug: the user should never have been allowed to configure this trigger on a WorkflowJob to begin with, since it is a Trigger>. 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-31236) Make "pipeline as code" the default user experience
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-31236 Make "pipeline as code" the default user experience Change By: Jesse Glick Status: Reopened Resolved Resolution: Duplicate 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] [promoted-builds-plugin] (JENKINS-31406) Promotion Status shows an excess of whitespace (missed one)
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31406 Re: Promotion Status shows an excess of whitespace (missed one) Code changed in jenkins User: Oleg Nenashev Path: src/main/resources/hudson/plugins/promoted_builds/PromotedBuildAction/index.jelly http://jenkins-ci.org/commit/promoted-builds-plugin/fa29d01baf125bd658aa384c7361b6c8fda2b1d0 Log: Merge pull request #84 from recena/JENKINS-31406 JENKINS-31406 Jelly tag l:pane breaks the UI Compare: https://github.com/jenkinsci/promoted-builds-plugin/compare/79e2c8e063cd...fa29d01baf12 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-31236) Make "pipeline as code" the default user experience
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-31236 Make "pipeline as code" the default user experience Change By: Jesse Glick Labels: 2.0 pipeline 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] [promoted-builds-plugin] (JENKINS-31406) Promotion Status shows an excess of whitespace (missed one)
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31406 Re: Promotion Status shows an excess of whitespace (missed one) Code changed in jenkins User: Manuel Recena Path: src/main/resources/hudson/plugins/promoted_builds/PromotedBuildAction/index.jelly http://jenkins-ci.org/commit/promoted-builds-plugin/ad17d3d03c86698e9646084b17d7c834768e9138 Log: JENKINS-31406 Jelly tag l:pane breaks the UI 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-31236) Make "pipeline as code" the default user experience
Title: Message Title Jesse Glick reopened an issue cannot edit labels while closed Jenkins / JENKINS-31236 Make "pipeline as code" the default user experience Change By: Jesse Glick Resolution: Duplicate Status: Closed Reopened 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-pipeline-plugin] (JENKINS-30198) Pipeline Jobs start even after previous job fails
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-30198 Pipeline Jobs start even after previous job fails Change By: Jesse Glick Labels: pipeline 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] [delivery-pipeline-plugin] (JENKINS-29639) Allow promotion from pipeline view
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-29639 Allow promotion from pipeline view Change By: Jesse Glick Labels: pipeline promotion 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] [workflow-plugin] (JENKINS-32780) Parameterize Multibranch Pipeline via Jenkinsfile
Title: Message Title Jesse Glick resolved as Not A Defect See Snippet Generator for the properties step. Jenkins / JENKINS-32780 Parameterize Multibranch Pipeline via Jenkinsfile Change By: Jesse Glick Status: Open Resolved Resolution: Not A Defect 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] [workflow-plugin] (JENKINS-32768) [pipeline multibranch] Lost configuration using Single Source
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-32768 [pipeline multibranch] Lost configuration using Single Source Change By: Jesse Glick Labels: multibranch plugin workflow 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-27635) Downstream build can start running before upstream build has completed
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-27635 Downstream build can start running before upstream build has completed Change By: Jesse Glick Labels: pipeline trigger 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-pipeline-plugin] (JENKINS-31012) build-pipeline-plugin requires absolute URLs
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-31012 build-pipeline-plugin requires absolute URLs Change By: Jesse Glick Labels: pipeline plugin 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] [promoted-builds-plugin] (JENKINS-32993) PROMOTED_ID doesn't expose timestamp after JENKINS-24380
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32993 Re: PROMOTED_ID doesn't expose timestamp after JENKINS-24380 Code changed in jenkins User: Oleg Nenashev Path: src/main/java/hudson/plugins/promoted_builds/Promotion.java http://jenkins-ci.org/commit/promoted-builds-plugin/66e9432878c161530522d54ca62e5188e2783b5e Log: Merge pull request #85 from fbelzunc/ JENKINS-32993 [FIXED JENKINS-32993] Expose PROMOTED_TIMESTAMP Compare: https://github.com/jenkinsci/promoted-builds-plugin/compare/fa29d01baf12...66e9432878c1 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] [promoted-builds-plugin] (JENKINS-32993) PROMOTED_ID doesn't expose timestamp after JENKINS-24380
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-32993 PROMOTED_ID doesn't expose timestamp after JENKINS-24380 Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed 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] [delivery-pipeline-plugin] (JENKINS-28146) Manual trigger step fails with the new version
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-28146 Manual trigger step fails with the new version Change By: Jesse Glick Labels: delivery jenkins manual pipeline plugin trigger 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] [promoted-builds-plugin] (JENKINS-31908) Promotions History sort in a job is wrong
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31908 Re: Promotions History sort in a job is wrong Code changed in jenkins User: Benjamin Baumann Path: src/main/java/hudson/plugins/promoted_builds/Promotion.java http://jenkins-ci.org/commit/promoted-builds-plugin/13c3a197ffdc3e3a241b96ed75d8ca95cabc5833 Log: Sort Promotion By Number Instead of sorting promotions by id (e.g. #42), sorts promotions by number (e.g. 42). Fixes the display of the promotion list history for a job. [FIXED JENKINS-31908] 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] [promoted-builds-plugin] (JENKINS-31908) Promotions History sort in a job is wrong
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31908 Re: Promotions History sort in a job is wrong Code changed in jenkins User: Oleg Nenashev Path: src/main/java/hudson/plugins/promoted_builds/Promotion.java http://jenkins-ci.org/commit/promoted-builds-plugin/b2ca190613909df2b44e27062ff1b4b066620a74 Log: Merge pull request #78 from bbaumann/master [FIXED JENKINS-31908] - Sort Promotion By Number Compare: https://github.com/jenkinsci/promoted-builds-plugin/compare/66e9432878c1...b2ca19061390 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] [promoted-builds-plugin] (JENKINS-31908) Promotions History sort in a job is wrong
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-31908 Promotions History sort in a job is wrong Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed 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] [delivery-pipeline-plugin] (JENKINS-27290) Communication Error, Syntax Problem
Title: Message Title Jesse Glick resolved as Cannot Reproduce Jenkins / JENKINS-27290 Communication Error, Syntax Problem Change By: Jesse Glick Status: Reopened Resolved Resolution: Cannot Reproduce 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-pipeline-plugin] (JENKINS-27001) On Windows installations if the pipeline view is set to show more than 200 jobs CPU is pushed to 100% causing the system to freeze
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-27001 On Windows installations if the pipeline view is set to show more than 200 jobs CPU is pushed to 100% causing the system to freeze Change By: Jesse Glick Labels: cpu performance 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] [copyartifact-plugin] (JENKINS-33003) Copy Artifacts from Another Projects Strange Behavior
Title: Message Title Esteban Vargas updated an issue Jenkins / JENKINS-33003 Copy Artifacts from Another Projects Strange Behavior Change By: Esteban Vargas Summary: Copy Artifacts from Another Projects Extrange Strange Behavior 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] [delivery-pipeline-plugin] (JENKINS-27290) Communication Error, Syntax Problem
Title: Message Title Jesse Glick reopened an issue cannot edit labels on a closed issue Jenkins / JENKINS-27290 Communication Error, Syntax Problem Change By: Jesse Glick Resolution: Cannot Reproduce Status: Closed Reopened 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] [delivery-pipeline-plugin] (JENKINS-27290) Communication Error, Syntax Problem
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-27290 Communication Error, Syntax Problem Change By: Jesse Glick Labels: JSON pipeline 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-17945) Downstream Dependency has broken, Also breaks Dependency Graph Plugin, and Build Pipeline Plugin
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-17945 Downstream Dependency has broken, Also breaks Dependency Graph Plugin, and Build Pipeline Plugin Change By: Jesse Glick Labels: Dependency Pipeline downstream 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] [ghprb-plugin] (JENKINS-32556) Workflow plugin now Pipeline crashes with GitHub Pull Request Builder plugin
Title: Message Title Faheem Nadeem commented on JENKINS-32556 Re: Workflow plugin now Pipeline crashes with GitHub Pull Request Builder plugin Cool... That seems a better approach than using ghprb. Do you have an expected timeline for JENKINS-32749 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-pipeline-plugin] (JENKINS-27001) On Windows installations if the pipeline view is set to show more than 200 jobs CPU is pushed to 100% causing the system to freeze
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-27001 On Windows installations if the pipeline view is set to show more than 200 jobs CPU is pushed to 100% causing the system to freeze Change By: Jesse Glick Labels: cpu pipeline 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] [sctmexecutor-plugin] (JENKINS-28304) save build step failed
Title: Message Title Edwin Chung commented on JENKINS-28304 Re: save build step failed Workaround using the "Advanced" button. 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] [nunit-plugin] (JENKINS-32999) Failed to transform nunit3 TestResult.xml
Title: Message Title Andrey Tretjakov commented on JENKINS-32999 Re: Failed to transform nunit3 TestResult.xml Paul Hicks, thank you. It works for me. 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] [nunit-plugin] (JENKINS-32999) Failed to transform nunit3 TestResult.xml
Title: Message Title Andrey Tretjakov updated an issue Jenkins / JENKINS-32999 Failed to transform nunit3 TestResult.xml Change By: Andrey Tretjakov ERROR: Step ‘Publish NUnit test result report’ aborted due to exception: hudson.util.IOException2: Could not transform the NUnit report. Please report this issue to the plugin author at hudson.plugins.nunit.NUnitArchiver.invoke(NUnitArchiver.java:68) at hudson.plugins.nunit.NUnitArchiver.invoke(NUnitArchiver.java:26) at hudson.FilePath.act(FilePath.java:990) at hudson.FilePath.act(FilePath.java:968) at hudson.plugins.nunit.NUnitPublisher.perform(NUnitPublisher.java:145) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:723) at hudson.model.Build$BuildExecution.post2(Build.java:185) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:668) at hudson.model.Run.execute(Run.java:1763) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)Caused by: org.xml.sax.SAXParseException; systemId: file:/C:/Jenkins/jobs/ ob.kontur.ru x /workspace/temporary-junit-reports/temp-junit.xml; lineNumber: 2; columnNumber: 3; Content is not allowed in prolog. at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(Unknown Source) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Unknown Source) at javax.xml.parsers.DocumentBuilder.parse(Unknown Source) at hudson.plugins.nunit.NUnitReportTransformer.splitJUnitFile(NUnitReportTransformer.java:102) at hudson.plugins.nunit.NUnitReportTransformer.transform(NUnitReportTransformer.java:72) at hudson.plugins.nunit.NUnitArchiver.invoke(NUnitArchiver.java:63) ... 13 more Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [test-results-analyzer-plugin] (JENKINS-32990) Link available in the Test report analyzer plugin is not correct if the testcases name has '/' character in it
Title: Message Title best best commented on JENKINS-32990 Re: Link available in the Test report analyzer plugin is not correct if the testcases name has '/' character in it It is not just the / character that needs to be replaced. We have the same issue with brackets (), @ symbol and " quotes. ie Results Analyzer links look like: ...1/testReport/(root)/TestClass/MyTest(george@gmail.com,%20sometext,%20False) should be ...1/testReport/(root)/TestClass/MyTest_george_bob_gmail_com_sometextFalse/ There is probably a list of other characters that needs to be replaced as well... 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] [test-results-analyzer-plugin] (JENKINS-32990) Link available in the Test report analyzer plugin is not correct if the testcases name has '/' character in it
Title: Message Title best best edited a comment on JENKINS-32990 Re: Link available in the Test report analyzer plugin is not correct if the testcases name has '/' character in it It is not just the / character that needs to be replaced. We have the same issue with brackets (), @ symbol , comma and " quotes.ie Results Analyzer links look like:...1/testReport/(root)/TestClass/MyTest(george@gmail.com,%20sometext,%20False)should be...1/testReport/(root)/TestClass/MyTest_george_bob_gmail_com__sometext__False_/There is probably a list of other characters that needs to be replaced as well... 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] [test-results-analyzer-plugin] (JENKINS-32990) Link available in the Test report analyzer plugin is not correct if the testcases name has '/' character in it
Title: Message Title best best edited a comment on JENKINS-32990 Re: Link available in the Test report analyzer plugin is not correct if the testcases name has '/' character in it It is not just the / character that needs to be replaced. We have the same issue with brackets (), @ symbol, comma and " quotes.ie Results Analyzer links look like:...1/testReport/(root)/TestClass/MyTest(george@gmail.com,%20sometext,%20False)should be...1/testReport/(root)/TestClass/ MyTest_george_bob_gmail_com__sometext__False_ MyTest_george_bob_gmail_com\_\_sometext\_\_False_ /There is probably a list of other characters that needs to be replaced as well... 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] [test-results-analyzer-plugin] (JENKINS-32990) Link available in the Test report analyzer plugin is not correct if the testcases name has '/' character in it
Title: Message Title best best edited a comment on JENKINS-32990 Re: Link available in the Test report analyzer plugin is not correct if the testcases name has '/' character in it It is not just the / character that needs to be replaced. We have the same issue with brackets (), @ symbol, comma and " quotes spaces .ie Results Analyzer links look like:...1/testReport/(root)/TestClass/MyTest(george@gmail.com,%20sometext,%20False)should be...1/testReport/(root)/TestClass/MyTest_george_bob_gmail_com\_\_sometext\_\_False_/There is probably a list of other characters that needs to be replaced as well... 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] [workflow-plugin] (JENKINS-32767) Stuck branch indexing blocks forbids any build to start
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-32767 Stuck branch indexing blocks forbids any build to start Change By: Jesse Glick Labels: robustness 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] [scm-api-plugin] (JENKINS-32768) [pipeline multibranch] Lost configuration using Single Source
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-32768 [pipeline multibranch] Lost configuration using Single Source Rarely tested, since there is not much point in using this SCM source: you would need to manually configure every branch. The cause is obvious from code inspection: the fields have no public getters. Should be simple to fix, and demonstrate using a functional test calling configRoundTrip using a mock Builder which takes an SCMSource field. Change By: Jesse Glick Component/s: scm-api-plugin Component/s: workflow-plugin Labels: multibranch workflow Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [nunit-plugin] (JENKINS-32999) Failed to transform nunit3 TestResult.xml
Title: Message Title Ben Langton commented on JENKINS-32999 Re: Failed to transform nunit3 TestResult.xml As an alternative, I am successfully using NUnit3 with the Jenkins NUnit plugin, by running the tests using a command line that includes: format=nunit2 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] [rebuild-plugin] (JENKINS-33014) Allow build environment variables to be re-used in re-build
Title: Message Title Ioannis Moutsatsos created an issue Jenkins / JENKINS-33014 Allow build environment variables to be re-used in re-build Issue Type: Improvement Assignee: ragesh_nair Attachments: Untitled_Clipping_021816_102315_AM.jpg Components: rebuild-plugin Created: 18/Feb/16 3:24 PM Environment: Jenkins v1.596.2 Parameterized Trigger Plugin v2.29 Priority: Minor Reporter: Ioannis Moutsatsos Currently although build parameters are re-used not re-using certain build environment variables can easily cause a rebuild to fail. As a result, I suggest to include an option to allow a re-build to use a set of the environment variables from the original build. A use case similar to JENKINS-13647 is the Parameterized Trigger Plugin which sets predefined environment variables for a downstream project before triggering a build. When such a downstream project is re-build it typically fails, as although the build parameters are preserved, the predefined environment variables are not. Otherwise this is a great and extreme
[JIRA] [copyartifact-plugin] (JENKINS-33015) Promotion Level reverts back to QA Build on each configure
Title: Message Title Jason Hammond created an issue Jenkins / JENKINS-33015 Promotion Level reverts back to QA Build on each configure Issue Type: Bug Assignee: Unassigned Attachments: promoterevert.PNG Components: copyartifact-plugin Created: 18/Feb/16 3:24 PM Priority: Minor Reporter: Jason Hammond I have a Deploy job setup to deploy to UAT environment. I have set Copy Artifacts from another project : Latest Promoted Build : Promotion Level = QA Approved When I save is it fine. When I configure the job again, the Promotion level reverts back to QA Build. If I save the job and did not notice the Promotion level change it then sets this to the wrong promotion level. Is this a bug?
[JIRA] [copyartifact-plugin] (JENKINS-33015) Promotion Level reverts back to QA Build on each configure
Title: Message Title Jason Hammond updated an issue Jenkins / JENKINS-33015 Promotion Level reverts back to QA Build on each configure Change By: Jason Hammond I have a Deploy job setup to deploy to UAT environment.I have set Copy Artifacts from another project : Latest Promoted Build : Promotion Level = QA ApprovedWhen I save is it is fine.When I configure the job again, the Promotion level reverts back to QA Build.If I save the job and did not notice the Promotion level change it then sets this to the wrong promotion level.Is this a bug? 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] [cvs-plugin] (JENKINS-33016) Jenkins doesn't detect CVS polling on Pipeline (Workflow) Job
Title: Message Title Flávio Augusto Valones created an issue Jenkins / JENKINS-33016 Jenkins doesn't detect CVS polling on Pipeline (Workflow) Job Issue Type: Bug Assignee: Unassigned Components: cvs-plugin Created: 18/Feb/16 3:29 PM Environment: Jenkins 1.642.1 Pipeline (workflow-plugin) 1.13 Labels: scm cvs workflow Priority: Blocker Reporter: Flávio Augusto Valones Polling error on a Pipeline Job: java.lang.AbstractMethodError: you must override the new overload of compareRemoteRevisionWith at hudson.scm.SCM.compareRemoteRevisionWith(SCM.java:375) at org.jenkinsci.plugins.workflow.job.WorkflowJob.poll(WorkflowJob.java:507) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:526) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:555) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:119) at java.util.concur
[JIRA] [workflow-plugin] (JENKINS-32997) Pipeline job: Abort older builds which are running
Title: Message Title Leon Leon commented on JENKINS-32997 Re: Pipeline job: Abort older builds which are running This issue is related to JENKINS-27039 independently of user inputs. The Use Case is to make the last build able to abort older builds in a specific stage (and just one build performing some operations once daily). In other words, a specific stage should have only the last build which passed all older stages running on it. 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] [workflow-plugin] (JENKINS-32997) Pipeline job: Abort older builds which are running
Title: Message Title Leon Leon edited a comment on JENKINS-32997 Re: Pipeline job: Abort older builds which are running Thank you for the information. This issue is related to [JENKINS-27039|https://issues.jenkins-ci.org/browse/JENKINS-27039] independently of user inputs. The Use Case is to make the last build able to abort older builds in a specific stage (and just one build performing some operations once daily).In other words, a specific stage should have only the last build which passed all older stages running on it. 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] [workflow-plugin] (JENKINS-32997) Pipeline job: Abort older builds which are running
Title: Message Title Leon Leon edited a comment on JENKINS-32997 Re: Pipeline job: Abort older builds which are running Thank you for the information.This issue is related to [JENKINS-27039|https://issues.jenkins-ci.org/browse/JENKINS-27039] independently of user inputs. The Use Case is to make the last build able to abort older builds in a specific stage (and by doing so just one build performing will perform some operations once daily for example ).In other words, a specific stage should have only the last build which passed all older stages running on it. 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] [workflow-plugin] (JENKINS-32997) Pipeline job: Abort older builds which are running
Title: Message Title Leon Leon edited a comment on JENKINS-32997 Re: Pipeline job: Abort older builds which are running Thank you for the information.This issue is related to [JENKINS-27039|https://issues.jenkins-ci.org/browse/JENKINS-27039] independently of user inputs. The Use Case is to make the last build able to abort older builds in a specific stage (and by doing so , just one build will perform some operations once daily for example).In other words, a specific stage should have only the last build which passed all older stages running on it. 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] [git-plugin] (JENKINS-32767) GitSCMSource can hang in branch indexing, blocking builds
Title: Message Title Jesse Glick assigned an issue to Mark Waite Jenkins / JENKINS-32767 GitSCMSource can hang in branch indexing, blocking builds Change By: Jesse Glick Summary: Stuck GitSCMSource can hang in branch indexing blocks forbids any build to start , blocking builds Component/s: git-plugin Component/s: workflow-plugin Assignee: Jesse Glick Mark Waite Priority: Minor Major Labels: multibranch robustness workflow Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [workflow-plugin] (JENKINS-32766) 'Official' Groovy XML authoring doesn't work in pipeline: NoSuchMethodError
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-32766 'Official' Groovy XML authoring doesn't work in pipeline: NoSuchMethodError Change By: Jesse Glick Labels: groovy 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] [workflow-plugin] (JENKINS-32766) 'Official' Groovy XML authoring doesn't work in pipeline: NoSuchMethodError
Title: Message Title Jesse Glick assigned an issue to Kohsuke Kawaguchi Jenkins / JENKINS-32766 'Official' Groovy XML authoring doesn't work in pipeline: NoSuchMethodError Change By: Jesse Glick Assignee: Jesse Glick Kohsuke Kawaguchi 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] [workflow-plugin] (JENKINS-32767) Stuck branch indexing blocks forbids any build to start
Title: Message Title Jesse Glick commented on JENKINS-32767 Re: Stuck branch indexing blocks forbids any build to start Specifically "Executor #-1 for master : executing jenkins.branch.MultiBranchProject$BranchIndexing@…" … state=RUNNABLE cpu=0% (running in native) at java.net.SocketInputStream.socketRead0(Native Method) at … at org.eclipse.jgit.util.IO.readFully(IO.java:246) at org.eclipse.jgit.transport.PacketLineIn.readLength(PacketLineIn.java:186) at org.eclipse.jgit.transport.PacketLineIn.readString(PacketLineIn.java:138) at org.eclipse.jgit.transport.BasePackConnection.readAdvertisedRefsImpl(BasePackConnection.java:195) at org.eclipse.jgit.transport.BasePackConnection.readAdvertisedRefs(BasePackConnection.java:176) at org.eclipse.jgit.transport.TransportGitAnon$TcpFetchConnection.(TransportGitAnon.java:194) at org.eclipse.jgit.transport.TransportGitAnon.openFetch(TransportGitAnon.java:120) at org.eclipse.jgit.transport.FetchProcess.executeImp(FetchProcess.java:136) at org.eclipse.jgit.transport.FetchProcess.execute(FetchProcess.java:122) at org.eclipse.jgit.transport.Transport.fetch(Transport.java:1138) at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:130) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.fetch(JGitAPIImpl.java:674) at jenkins.plugins.git.AbstractGitSCMSource.retrieve(AbstractGitSCMSource.java:171) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:143) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:295) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:151) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:106) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:408) The immediate problem I see is that socket reads in the Oracle JRE are not interruptible, so using a native SCM client is a bad idea, unless that client is very careful to impose read timeouts on all connections, which apparently the JGit implementation is failing to do. (This code is not calling setSoTimeout.) Would be better to use the CLI Git implementation (cf. JENKINS-31924). Other builds are blocked on the cache lock: "Executor #-1 for master : executing something/master #123" … state=WAITING cpu=86% - waiting on <…> (a java.util.concurrent.locks.ReentrantLock$NonfairSync) - locked <…> (a java.util.concurrent.locks.ReentrantLock$NonfairSync) owned by "Executor #-1 for master : executing jenkins.branch.MultiBranchProject$BranchIndexing@…" … at … at java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java:285) at jenkins.plugins.git.AbstractGitSCMSource.retrieve(AbstractGitSCMSource.java:120) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:233) at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:77) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:206) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:408) This code should be using lockInterruptibly, I think.
[JIRA] [workflow-plugin] (JENKINS-32756) Not possible to copy a workflow based job
Title: Message Title Jesse Glick resolved as Incomplete Never heard of such a link. Can you attach a screenshot? Copy of HTML text for this link? Any particular plugin offering such a function? From Googling I can find this plugin, so if you are using it, move the issue to the appropriate component and add the workflow label and get it mentioned in COMPATIBILITY.md. Jenkins / JENKINS-32756 Not possible to copy a workflow based job Change By: Jesse Glick Status: Open Resolved Resolution: Incomplete 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.
