[JIRA] (JENKINS-42284) 'chcp' is not recognized as an internal or external command, operable program or batch file.
Title: Message Title Lionel Cabasson commented on JENKINS-42284 Re: 'chcp' is not recognized as an internal or external command, operable program or batch file. Hello, Maybe this user does not have access right to chcp or the user PATH environment variable does not contain its parent forlder. Could you try running Jenkins with the Local system user for the sake of testing ? I wanted to wait a little bit to see if there was any other user who encountered the same issue but it seems you're the only one so it's probably an environment specific problem. By the way, I will think about adding an option not to run chcp so that one can disable it if any problem arise. Regards Lionel Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42549) Git checkout fails when running multiple jobs on same slave with 'java.lang.IllegalStateException: zip file closed' exception
Title: Message Title Waldemar Kotarba commented on JENKINS-42549 Re: Git checkout fails when running multiple jobs on same slave with 'java.lang.IllegalStateException: zip file closed' exception Same issue with Jenkins 2.19.2, Maven IntegrationPlugin 2.15.1, Java OpenJDK 1.7.0_111, Debian 8 64-bit Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43106) pipeline job hangs sporadically at checkout GitSCM
Title: Message Title Lev Tartakovsky updated an issue Jenkins / JENKINS-43106 pipeline job hangs sporadically at checkout GitSCM Change By: Lev Tartakovsky Attachment: Capture.PNG Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43122) Configure HTTPS to Jenkins Installer
Title: Message Title Satyanarayana Guptha created an issue Jenkins / JENKINS-43122 Configure HTTPS to Jenkins Installer Issue Type: Bug Assignee: Unassigned Components: core Created: 2017/Mar/27 5:57 AM Environment: Jenkins - 2.7.1, Installer SVN,TFS,RTC,GIT,MAVEN,ANT,JAVA Priority: Critical Reporter: Satyanarayana Guptha HI, Currently we have installed Jenkins installer in windows server and trying to configure HTTPS to Jenkins installer to browse the Jenkins using https link. And we have genrated SSL certificate and have put the jks file in secrets folder. once the setup is completed we are not able to start the jenkins as service and it is starting only using command prompt.And even we are not able to access using https. The steps we followed while configuring the SSL to jenkins is https://wiki.jenkins-ci.org/display/JENKINS/Starting+and+Accessing+Jenkins. Kindly please help us to resolve the issue asap. Add Comment
[JIRA] (JENKINS-42903) HTML in description is always escaped
Title: Message Title 琴挑文君 Ma edited a comment on JENKINS-42903 Re: HTML in description is always escaped i met this issue on my jenkins. jenkins 2.32.3 !image-2017-03-27-13-47-34-456.png! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42903) HTML in description is always escaped
Title: Message Title 琴挑文君 Ma edited a comment on JENKINS-42903 Re: HTML in description is always escaped i met this issue on my jenkins. jenkins 2.32.3 extensible-choice-parameter- 1.3.4 !image-2017-03-27-13-47-34-456.png! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42903) HTML in description is always escaped
Title: Message Title 琴挑文君 Ma updated an issue Jenkins / JENKINS-42903 HTML in description is always escaped Change By: 琴挑文君 Ma Attachment: image-2017-03-27-13-47-34-456.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42903) HTML in description is always escaped
Title: Message Title 琴挑文君 Ma commented on JENKINS-42903 Re: HTML in description is always escaped Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43121) Unable to install jenkins in windows 7
Title: Message Title
venki v created an issue
Jenkins / JENKINS-43121
Unable to install jenkins in windows 7
Issue Type:
Bug
Assignee:
Unassigned
Components:
jenkins-cloudformation
Created:
2017/Mar/27 5:47 AM
Environment:
Windows 7
Labels:
Jenkins installation
Priority:
Major
Reporter:
venki v
Hi Team, I am unable to install 2.32.3 war file in windows. I had downloaded the file from windows and trying to install by following the steps. Prerequisites: Java 8 Update 121 Jenkins war 2.32.3 I open cmd and use the below command java -jar jenkins.war But the installation fails and says "Jenkins stopped". The below is the error and I am not able ot correlate what is the error . WOuld be great if you can suggest on the same. ERROR SNIPPET: ←[33mMar 27, 2017 11:15:10 AM org.eclipse.jetty.util.log.JavaUtilLog warn WARNING: FAILED ServerConnector@27aa33{HTTP/1.1}{0.0.0.0:8080}: java.net.BindEx eption: Address already in use: bind java.net.BindException: Address already in use: bind at sun.nio.ch.Net.bind0(Native Method) at sun.nio.ch.Net.bind(Unknown Source) at sun.nio.ch.Net.bind(Unknown Source) at sun.nio.ch.ServerSocketChannelImpl.bind(Unknown Source) at sun.nio.ch.ServerSocketAdaptor.bind(Unknown Source) at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:3 1) at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNe workConnector.java:80) at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.jav :236) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLif Cycle.java:68) at org.eclips
[JIRA] (JENKINS-43120) when rebuild job started by timer, user build vars are empty
Title: Message Title 琴挑文君 Ma updated an issue Jenkins / JENKINS-43120 when rebuild job started by timer, user build vars are empty Change By: 琴挑文君 Ma jenkins 2.32.2userbuild vars plugin 1.5 when rebuild one job started by timer the user build vars are empty. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43120) when rebuild job started by timer, user build vars are empty
Title: Message Title 琴挑文君 Ma updated an issue Jenkins / JENKINS-43120 when rebuild job started by timer, user build vars are empty Change By: 琴挑文君 Ma Summary: when rebuild job started by timer, user build vars are empty Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43120) when rebuild user build vars are empty
Title: Message Title 琴挑文君 Ma updated an issue Jenkins / JENKINS-43120 when rebuild user build vars are empty Change By: 琴挑文君 Ma Attachment: 1.png Attachment: 2.png Attachment: 3.png Attachment: 4.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42994) In some situations, the 're-run' button will not trigger a build and not give any feedback of failure.
Title: Message Title James Dumay resolved as Cannot Reproduce Jenkins / JENKINS-42994 In some situations, the 're-run' button will not trigger a build and not give any feedback of failure. Change By: James Dumay Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43120) when rebuild user build vars are empty
Title: Message Title 琴挑文君 Ma created an issue Jenkins / JENKINS-43120 when rebuild user build vars are empty Issue Type: Bug Assignee: Unassigned Components: build-user-vars-plugin Created: 2017/Mar/27 5:22 AM Environment: jenkins 2.32.2 userbuild vars plugin 1.5 Priority: Minor Reporter: 琴挑文君 Ma jenkins 2.32.2 userbuild vars plugin 1.5 when rebuild one job the user build vars are empty. Add Comment
[JIRA] (JENKINS-42872) Inputs with multiple approvers do not work
Title: Message Title Michael Neale commented on JENKINS-42872 Re: Inputs with multiple approvers do not work hanks justin that is the opposite to what Ivan Meredith saw though - so I am not sure what is going on. In my case - I can't even get classic to work with this, so not sure what is going on. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43117) Run declarative pipeline job with parameters fails if description is null
Title: Message Title Michael Neale commented on JENKINS-43117 Re: Run declarative pipeline job with parameters fails if description is null Fix: https://github.com/jenkinsci/blueocean-plugin/pull/928 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43117) Run declarative pipeline job with parameters fails if description is null
Title: Message Title Michael Neale updated JENKINS-43117 Jenkins / JENKINS-43117 Run declarative pipeline job with parameters fails if description is null Change By: Michael Neale Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42872) Inputs with multiple approvers do not work
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-42872
Inputs with multiple approvers do not work
Change By:
James Dumay
*Notes*This will work when there is a single approver specified but not when there are multiple. Blue Ocean will respond with a 400 error. Due to JENKINS-42920 the user will not receive feedback on why they are not allowed to proceed or any other error, which made this problem more confusing.To run these scenarios you will need two users - 'alice' and 'bob'.*Scenario 1 - current user is 'alice', single approver*This works fine in Blue Ocean{code}node {echo 'hello world'input message: "Do you want to approve this job to deploy to production?", ok: "OK", submitter: "alice"}{code}*Scenario 2 - current user is 'alice', multiple approvers*{code}node {echo 'hello world'input message: "Do you want to approve this job to deploy to production?", ok: "OK", submitter: "alice, bob"}{code}*Original request*I use input step like below:{code}timeout(time: 5, unit: "DAYS") \{ input message: "Do you want to approve this job to deploy to production?", ok: "OK", submitter: "A, B, C"}{code}can not use multi submitter in Blue Ocean UI, but it works fine in the old UI.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-42872) Inputs with multiple approvers do not work
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-42872
Inputs with multiple approvers do not work
Change By:
James Dumay
*Notes*This will work when there is a single approver specified but not when there are multiple. Blue Ocean will respond with a 400 error. Due to JENKINS-42920 the user will not receive feedback on why they are not allowed to proceed or any other error, which made this problem more confusing.To run these scenarios you will need two users - 'alice' and 'bob'.*Scenario 1 - current user is 'alice', single approver*This works fine in Blue Ocean{code}node {echo 'hello world'input message: "Do you want to approve this job to deploy to production?", ok: "OK", submitter: "alice"}{code}*Scenario 2 - current user is 'alice', multiple approvers*{code}node {echo 'hello world'input message: "Do you want to approve this job to deploy to production?", ok: "OK", submitter: "alice,bob"}{code}*Original request*I use input step like below:{code}timeout(time: 5, unit: "DAYS") \{ input message: "Do you want to approve this job to deploy to production?", ok: "OK", submitter: "A, B, C"}{code}can not use multi submitter in Blue Ocean UI, but it works fine in the old UI.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-43117) Run declarative pipeline job with parameters fails if description is null
Title: Message Title Michael Neale started work on JENKINS-43117 Change By: Michael Neale Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43117) Run declarative pipeline job with parameters fails if description is null
Title: Message Title Michael Neale assigned an issue to Ivan Meredith Jenkins / JENKINS-43117 Run declarative pipeline job with parameters fails if description is null Change By: Michael Neale Assignee: Ivan Meredith Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42872) Inputs with multiple approvers do not work
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-42872
Inputs with multiple approvers do not work
Change By:
James Dumay
*Notes*This will work when there is a single approver specified but not when there are multiple. Blue Ocean will respond with a 400 error. Due to JENKINS-42920 the user will not receive feedback on why they are not allowed to proceed or any other error, which made this problem more confusing.To run these scenarios you will need two users - 'alice' and 'bob'.*Scenario 1 - current user is 'alice', single approver*This works fine in Blue Ocean{code}node {echo 'hello world'input message: "Do you want to approve this job to deploy to production?", ok: "OK", submitter: "alice" } {code}*Scenario 2 - current user is 'alice', multiple approvers*{code}node {echo 'hello world'input message: "Do you want to approve this job to deploy to production?", ok: "OK", submitter: "alice, bob" } {code}*Original request*I use input step like below:{code}timeout(time: 5, unit: "DAYS") \{ input message: "Do you want to approve this job to deploy to production?", ok: "OK", submitter: "A, B, C"}{code}can not use multi submitter in Blue Ocean UI, but it works fine in the old UI.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-42872) Inputs with multiple approvers do not work
Title: Message Title hanks justin commented on JENKINS-42872 Re: Inputs with multiple approvers do not work Michael Neale Thank you for your quick job, Seems there should be no space in submitter settings like below submitter: "A,B,C" the classic UI Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43083) Investigate how to improve unit and integration tests and avoid relying on E2E (ATH)
Title: Message Title Michael Neale commented on JENKINS-43083 Re: Investigate how to improve unit and integration tests and avoid relying on E2E (ATH) cc Ivan Meredith this might be worth researching too Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42959) Failed known_hosts verification for SSH agent
Title: Message Title Misa Travel commented on JENKINS-42959 Re: Failed known_hosts verification for SSH agent Michael Clarke The fact is that I already created the file manually and I have tried to make it run. I would like to highlight again that I am running Jenkins on Windows, which doesn't have OpenSSH, and as Jenkins manager, I may not have access to Windows to operate neither remotely nor locally. At the end, I have created the known_hosts using reference other known_hosts, but this is what I get: [03/27/17 10:24:43] [SSH] Opening SSH connection to fedora3.misatravel.org:22. [03/27/17 10:24:44] [SSH] WARNING: No entry currently exists in the Known Hosts file for this host. Connections will be denied until this new host and its associated key is added to the Known Hosts file. Key exchange was not finished, connection is closed. java.io.IOException: There was a problem while connecting to fedora3.misatravel.org:22 at com.trilead.ssh2.Connection.connect(Connection.java:818) at com.trilead.ssh2.Connection.connect(Connection.java:687) at com.trilead.ssh2.Connection.connect(Connection.java:601) at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:1265) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:790) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:785) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.io.IOException: Key exchange was not finished, connection is closed. at com.trilead.ssh2.transport.KexManager.getOrWaitForConnectionInfo(KexManager.java:93) at com.trilead.ssh2.transport.TransportManager.getConnectionInfo(TransportManager.java:230) at com.trilead.ssh2.Connection.connect(Connection.java:770) ... 9 more Caused by: java.io.IOException: The server hostkey was not accepted by the verifier callback at com.trilead.ssh2.transport.KexManager.handleMessage(KexManager.java:591) at com.trilead.ssh2.transport.TransportManager.receiveLoop(TransportManager.java:777) at com.trilead.ssh2.transport.TransportManager$1.run(TransportManager.java:489) ... 1 more [03/27/17 10:24:44] Launch failed - cleaning up connection [03/27/17 10:24:44] [SSH] Connection closed. Now, it is when I realize about the box "Host Key Verification Strategy" which was set up as "Known hosts file Verification Strategy", but you can see that it didn't work for me. So I change it to "Manually provided key Verification Strategy", and I put in the "SSH Key" the public key of the computer+user I want to access, but I get [03/27/17 10:32:10] [SSH] Opening SSH connection to fedora3.misatravel.org:22. [03/27/17 10:32:10] [SSH] WARNING: The SSH key for this host does not match the key required in the connection configuration. Connections will be denied until until the host key matches the configuration key. Key exchange was not finished, connection is closed. java.io.IOException: There was a problem while connecting to fedora3.misatravel.org:22 at com.trilead.ssh2.Connection.connect(Connection.java:818) at com.trilead.ssh2.Connection.connect(Connection.java:687) at com.trilead.ssh2.Connection.connect(Connection.java:601) at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:1265) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:790) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:785) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknow
[JIRA] (JENKINS-43119) Monitor Swam client on some port ?
Title: Message Title Vikas Kumar created an issue Jenkins / JENKINS-43119 Monitor Swam client on some port ? Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: swarm-plugin Created: 2017/Mar/27 2:30 AM Priority: Minor Reporter: Vikas Kumar Hello Everyone, I am using a number of Jenkins Slaves to connect to the master as below nohup java -jar /opt/swarm-client-3.3.jar -master http://:8080 -username -password -fsroot /var/jenkins_home & This works fine but I am looking to monitor the slaves on some port (TCP or UDP) so that I can use AWS ELB with Autoscaling. Is there a way out to open some port on the slave which can be monitored? Regards, Vikas Add Comment
[JIRA] (JENKINS-42872) Inputs with multiple approvers do not work
Title: Message Title Michael Neale commented on JENKINS-42872 Re: Inputs with multiple approvers do not work I am not able to reproduce the setup with the instructions, I can't get classic to accept submitting in any case given, and not sure what matrix settings to use. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42872) Inputs with multiple approvers do not work
Title: Message Title Michael Neale commented on JENKINS-42872 Re: Inputs with multiple approvers do not work hanks justin there is a fix in review for this, but it uses a deprecated API so trying to get the bottom of that... Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43118) User can access the Pipeline editor without a repository
Title: Message Title James Dumay created an issue Jenkins / JENKINS-43118 User can access the Pipeline editor without a repository Issue Type: Story Assignee: James Dumay Components: blueocean-pipeline-editor-plugin Created: 2017/Mar/27 2:00 AM Priority: Major Reporter: James Dumay We want to restore the link to the "Pipeline Playground" mode of the editor in a less obtrusive place. This was lost as the editor and creation was merged together Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-41737) Dashboard screen when there are no pipelines
Title: Message Title Michael Neale updated JENKINS-41737 Jenkins / JENKINS-41737 Dashboard screen when there are no pipelines Change By: Michael Neale Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43117) Run declarative pipeline job with parameters fails if description is null
Title: Message Title
Michael Neale updated an issue
Jenkins / JENKINS-43117
Run declarative pipeline job with parameters fails if description is null
Change By:
Michael Neale
If a parameter is configured via declarative pipeline, and no description is set, it will cause the "Run job" button "not work at all" inside blueocean. It should work, as descriptions are optional !image-2017-03-27-11-27-49-492.png|thumbnail! h4. Console stack trace {noformat}blueocean.js:7226 Uncaught Error: Invalid arg type for "markupText". Must be a string.at removeMarkupTags (blueocean.js:7226)at String.render (blueocean.js:4316)at ReactCompositeComponentWrapper._renderValidatedComponentWithoutOwnerOrContext (blueocean.js:84749)at ReactCompositeComponentWrapper._renderValidatedComponent (blueocean.js:84772)at ReactCompositeComponentWrapper.performInitialMount (blueocean.js:84314)at ReactCompositeComponentWrapper.mountComponent (blueocean.js:84210)at Object.mountComponent (blueocean.js:91223){noformat} h4. Example Job See - [ https://ci.blueocean.io/blue/organizations/jenkins/scratch%2Fbwalding%2Ftest-parameter/ ] {noformat}pipeline { agent any parameters {// Note the lack of descriptionstring(name: 'PERSON', defaultValue: 'Mr Jenkins') } stages {stage('Example') { steps {echo "Hello ${params.PERSON}" }} }}{noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-43117) Run declarative pipeline job with parameters fails if description is null
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-43117 Run declarative pipeline job with parameters fails if description is null Change By: Michael Neale Sprint: Blue Ocean 1.0-rc2 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43117) Run declarative pipeline job with parameters fails if description is null
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-43117 Run declarative pipeline job with parameters fails if description is null Change By: Michael Neale Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42872) Inputs with multiple approvers do not work
Title: Message Title Michael Neale updated JENKINS-42872 Jenkins / JENKINS-42872 Inputs with multiple approvers do not work Change By: Michael Neale Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43117) Run declarative pipeline job with parameters fails if description is null
Title: Message Title Ben Walding updated an issue Jenkins / JENKINS-43117 Run declarative pipeline job with parameters fails if description is null Change By: Ben Walding Issue Type: Improvement Bug Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43117) Run declarative pipeline job with parameters fails if description is null
Title: Message Title Ben Walding created an issue Jenkins / JENKINS-43117 Run declarative pipeline job with parameters fails if description is null Issue Type: Improvement Assignee: Unassigned Attachments: image-2017-03-27-11-27-49-492.png Components: blueocean-plugin Created: 2017/Mar/27 1:30 AM Environment: ci.blueocean.io Priority: Minor Reporter: Ben Walding If a parameter is configured via declarative pipeline, an no description is set, it will cause the "Run job" button "not work at all" inside blueocean.Console stack trace blueocean.js:7226 Uncaught Error: Invalid arg type for "markupText". Must be a string. at removeMarkupTags (blueocean.js:7226) at String.render (blueocean.js:4316) at ReactCompositeComponentWrapper._renderValidatedComponentWithoutOwnerOrContext (blueocean.js:84749) at ReactCompositeComponentWrapper._renderValidatedComponent (blueocean.js:84772) at ReactCompositeComponentWrapper.performInitialMount (blueocean.js:84314) at ReactCompositeComponentWrapper.mountComponent (blueocean.js:84210) at Object.mountComponent (blueocean.js:91223) Example Job See - https://ci.blueocean.io/blue/organizations/jenkins/scratch%2Fbwalding%2Ftest-parameter/
[JIRA] (JENKINS-43117) Run declarative pipeline job with parameters fails if description is null
Title: Message Title Ben Walding updated an issue Jenkins / JENKINS-43117 Run declarative pipeline job with parameters fails if description is null Change By: Ben Walding Environment: ci.blueocean.io + 1.0-rc2 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43117) Run declarative pipeline job with parameters fails if description is null
Title: Message Title
Ben Walding updated an issue
Jenkins / JENKINS-43117
Run declarative pipeline job with parameters fails if description is null
Change By:
Ben Walding
If a parameter is configured via declarative pipeline, an and no description is set, it will cause the "Run job" button "not work at all" inside blueocean. !image-2017-03-27-11-27-49-492.png|thumbnail! h4. Console stack trace{noformat}blueocean.js:7226 Uncaught Error: Invalid arg type for "markupText". Must be a string.at removeMarkupTags (blueocean.js:7226)at String.render (blueocean.js:4316)at ReactCompositeComponentWrapper._renderValidatedComponentWithoutOwnerOrContext (blueocean.js:84749)at ReactCompositeComponentWrapper._renderValidatedComponent (blueocean.js:84772)at ReactCompositeComponentWrapper.performInitialMount (blueocean.js:84314)at ReactCompositeComponentWrapper.mountComponent (blueocean.js:84210)at Object.mountComponent (blueocean.js:91223){noformat}h4. Example JobSee - https://ci.blueocean.io/blue/organizations/jenkins/scratch%2Fbwalding%2Ftest-parameter/{noformat}pipeline { agent any parameters {// Note the lack of descriptionstring(name: 'PERSON', defaultValue: 'Mr Jenkins') } stages {stage('Example') { steps {echo "Hello ${params.PERSON}" }} }}{noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-43116) Pipeline playground
Title: Message Title James Dumay created an issue Jenkins / JENKINS-43116 Pipeline playground Issue Type: New Feature Assignee: James Dumay Components: blueocean-pipeline-editor-plugin Created: 2017/Mar/27 1:20 AM Priority: Minor Reporter: James Dumay Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Iss
[JIRA] (JENKINS-42515) User education empty state updates
Title: Message Title James Dumay commented on JENKINS-42515 Re: User education empty state updates Note that this comment has been resolved. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43115) Lost pretty URLs on branch filtering
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-43115
Lost pretty URLs on branch filtering
Change By:
James Dumay
*Context* Sadly we seem to have lost pretty URLs for the branch filtering on the activity tab and now have a {{?branch=foo}} when we fixed JENKINS-42702. *In scope** Restore pretty URLs* Ensure that JENKINS-42702 still works* Update places that link to filtered activity so that they use the pretty urls
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43115) Lost pretty URLs on branch filtering
Title: Message Title James Dumay created an issue Jenkins / JENKINS-43115 Lost pretty URLs on branch filtering Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2017/Mar/27 1:03 AM Priority: Minor Reporter: James Dumay Sadly we seem to have lost pretty URLs for the branch filtering on the activity tab and now have a ?branch=foo when we fixed JENKINS-42702. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-42994) In some situations, the 're-run' button will not trigger a build and not give any feedback of failure.
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-42994 In some situations, the 're-run' button will not trigger a build and not give any feedback of failure. Change By: James Dumay Sprint: Blue Ocean 1. 1 0-rc2 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42105) Update all text copy for Github creation flow
Title: Message Title James Dumay updated JENKINS-42105 Jenkins / JENKINS-42105 Update all text copy for Github creation flow Change By: James Dumay Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43114) Artifact download button does not include pipeline.log
Title: Message Title
James Dumay created an issue
Jenkins / JENKINS-43114
Artifact download button does not include pipeline.log
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
download-all.png
Components:
blueocean-plugin
Created:
2017/Mar/27 12:00 AM
Priority:
Minor
Reporter:
James Dumay
Steps to reproduce
Setup a new Pipeline using the Jenkinsfile below
Run the Pipeline
Go to the run and click on the artifacts tab
Click Download All
There are no "real" artifacts, so the download all option will fail
Notes We display the log file as an artifact though Jenkins does not consider it an artifact. Example
node {
echo 'Hello world'
}
[JIRA] (JENKINS-42994) In some situations, the 're-run' button will not trigger a build and not give any feedback of failure.
Title: Message Title Michael Neale commented on JENKINS-42994 Re: In some situations, the 're-run' button will not trigger a build and not give any feedback of failure. I think this can stay out of current sprint, needs more time etc. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42994) In some situations, the 're-run' button will not trigger a build and not give any feedback of failure.
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-42994 In some situations, the 're-run' button will not trigger a build and not give any feedback of failure. Change By: Michael Neale Sprint: Blue Ocean 1. 0-rc2 1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43107) Support console annotations
Title: Message Title yacoub hossain commented on JENKINS-43107 Re: Support console annotations Thanks James Dumay, i will be eagerly awaiting, btw, am loving the blue ocean ui, very slick Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43113) Release engineering
Title: Message Title James Dumay created an issue Jenkins / JENKINS-43113 Release engineering Issue Type: Epic Assignee: Unassigned Components: blueocean-plugin Created: 2017/Mar/26 11:27 PM Priority: Minor Reporter: James Dumay Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscr
[JIRA] (JENKINS-43079) Move publishing to ci.jenkins.io or automated location
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-43079 Move publishing to ci.jenkins.io or automated location Change By: James Dumay Sprint: Blue Ocean 1.1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43107) Support console annotations
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-43107 Support console annotations yacoub hossain thanks for filing! We are going to provide better support for the build step (linking to downstream jobs - see JENKINS-38339) but it will take a bit more time to support log annotations in the way you are used to them in classic. Change By: James Dumay *Notes*Jenkins uses the console annotator extension point to display links and other elements within the console log. This extension point is a java extension point and could be moved to a js extension.*Original request* When using Blue Ocean UI, the console output is just plain text, wheras the classic UI had the option of plain text but by default showed a smarter console output that would, for instance, contain clickable url links to downstream jobs, or archived artifacts. That would be a very cool thing to have again in the Blue Ocean UI. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-43107) Support console annotations
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-43107 Support console annotations Change By: James Dumay Summary: Blue Ocean Support console output, only outputs plain text annotations Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42994) In some situations, the 're-run' button will not trigger a build and not give any feedback of failure.
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-42994 In some situations, the 're-run' button will not trigger a build and not give any feedback of failure. Change By: James Dumay Sprint: Blue Ocean 1.0-rc2 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41200) Developer can see ANSI color in log file
Title: Message Title Michael Neale commented on JENKINS-41200 Re: Developer can see ANSI color in log file I think some of this could be classified as "tech debt" as the log has been a big neglected since it was created. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41200) Developer can see ANSI color in log file
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-41200 Developer can see ANSI color in log file Change By: Michael Neale Labels: technical-debt Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42994) In some situations, the 're-run' button will not trigger a build and not give any feedback of failure.
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-42994 In some situations, the 're-run' button will not trigger a build and not give any feedback of failure. Change By: Michael Neale Labels: blueocean technical-debt Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43112) Add Maven 3.3 in the Test Harness Tools
Title: Message Title Cyrille Le Clerc created an issue Jenkins / JENKINS-43112 Add Maven 3.3 in the Test Harness Tools Issue Type: New Feature Assignee: Cyrille Le Clerc Components: core Created: 2017/Mar/26 8:30 PM Priority: Minor Reporter: Cyrille Le Clerc The jenkins-test-harness-tools does not yet bundle Maven 3.3, the latest version is Maven 3.1. We need Maven 3.3 for some tests of the Pipeline Maven Plugin. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-43111) Upgrade 1.x to 2.x: upgrade wizard disappears when auto refresh is enabled
Title: Message Title
Bert Jan Schrijver updated an issue
Jenkins / JENKINS-43111
Upgrade 1.x to 2.x: upgrade wizard disappears when auto refresh is enabled
Change By:
Bert Jan Schrijver
*Short version*When auto refresh of the Jenkins GUI is enabled prior to starting a 1.6 -> 2.x upgrade, the upgrade wizard closes after a few seconds due to the auto refresh kicking in. *Versions/software used* * Jenkins 1.6:{{docker run -p 8080:8080 -p 5:5 -v /Users/bertjan/jenkins/home:/var/jenkins_home jenkins:1.651.3}} * Jenkins 2.3:{{docker run -p 8080:8080 -p 5:5 -v /Users/bertjan/jenkins/home:/var/jenkins_home jenkins:2.32.3}} *Reproduction path* * Install Jenkins 1.6 * Stop the 1.6 instance, start a Jenkins 2.3 instance and point it to the same homedir used for the 1.6 instance * When the Jenkins 2.3 instance boots, don't log in and start the upgrade wizard just yet * First, make sure that auto refresh is enabled (by clicking "ENABLE AUTO REFRESH" in the top right corner) * Click 'Upgrade now' to start the upgrade wizard' * Click 'Continue'. The upgrade starts. * Wait a bit for the autorefresh to kick in. This closes the upgrade wizard dialog window.The upgrade does continue (looking at the logs in my terminal) but there's no way of viewing its progress in the GUI.This doesn't happen when auto refresh isn't enabled. Priority *Additional info*I marked this issue with priority "major" because this can have quite a negative influence on the trust of that new 2.x users have in the upgrade . Imagine finally gaining enough courage for taking the step to upgrade your mission-critical installation to 2.x, only to see the upgrade wizard disappear after a few seconds and being completely in the blue whether the upgrade succeeded or failed. I can hear managers shouting "rollback! rollback!" already ;) I think it would be alright to just disable auto refresh before the upgrade wizard starts. If the user really wants auto refresh, he/she will enable it again after the upgrade.
Add Comment
[JIRA] (JENKINS-43111) Upgrade 1.x to 2.x: upgrade wizard disappears when auto refresh is enabled
Title: Message Title Bert Jan Schrijver created an issue Jenkins / JENKINS-43111 Upgrade 1.x to 2.x: upgrade wizard disappears when auto refresh is enabled Issue Type: Bug Assignee: Unassigned Components: core Created: 2017/Mar/26 7:02 PM Environment: Upgrade from 1.651.3 to 2.32.3 Priority: Major Reporter: Bert Jan Schrijver Short version When auto refresh of the Jenkins GUI is enabled prior to starting a 1.6 -> 2.x upgrade, the upgrade wizard closes after a few seconds due to the auto refresh kicking in. Versions/software used Jenkins 1.6: docker run -p 8080:8080 -p 5:5 -v /Users/bertjan/jenkins/home:/var/jenkins_home jenkins:1.651.3 Jenkins 2.3: docker run -p 8080:8080 -p 5:5 -v /Users/bertjan/jenkins/home:/var/jenkins_home jenkins:2.32.3 Reproduction path Install Jenkins 1.6 Stop the 1.6 instance, start a Jenkins 2.3 instance and point it to the same homedir used for the 1.6 instance When the Jenkins 2.3 instance boots, don't log in and start the upgrade wizard just yet First, make sure that auto refresh is enabled (by clicking "ENABLE AUTO REFRESH" in the top right corner)
[JIRA] (JENKINS-42955) Add support for folder credentials
Title: Message Title Raul Arabaolaza commented on JENKINS-42955 Re: Add support for folder credentials Makes sense, I will fix this ASAP Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42931) Upload spec does not resolve placeholders in target path
Title: Message Title Dima Nevelev commented on JENKINS-42931 Re: Upload spec does not resolve placeholders in target path Josh Hasner you right, there is a problem with the placeholders when using a full path. We are working on this and will update any progress in the following Jira issue: https://www.jfrog.com/jira/browse/HAP-897 Sascha Kolberg we still unable to reproduce your case (case of relative to workspace pattern). Please provide us the content of your working directory. Feel free to mask sensitive data. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42675) Override default NodeJS registry when installing in global mode on Global Tools Configuration page
Title: Message Title Nikolas Falco commented on JENKINS-42675 Re: Override default NodeJS registry when installing in global mode on Global Tools Configuration page In master I've changed the no proxy host management so all no proxy hosts are put in the environment variable NO_PROXY, a list of host comma separated. Keep in mind that wild card seems not be supported by npm. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43102) Incorrect identification of arm binary at nodejs.org
Title: Message Title Nikolas Falco commented on JENKINS-43102 Re: Incorrect identification of arm binary at nodejs.org The only way that I can see is configure NodeJS tools with "Extract zip/tar" instead "install from nodejs.org". About JENKINS-43066 plese have a look the known limitation section in our wiki page for a solution. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43102) Incorrect identification of arm binary at nodejs.org
Title: Message Title Nikolas Falco assigned an issue to Nikolas Falco Jenkins / JENKINS-43102 Incorrect identification of arm binary at nodejs.org Change By: Nikolas Falco Assignee: Nikolas Falco Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43066) With pipeline, tools does not setup properly the environment
Title: Message Title
Nikolas Falco closed an issue as Fixed
I've try the pipeline script you post at stackoverflow on our jenkins installation and it works. Follow the expected output:
[Pipeline] node
Running on master in /var/lib/jenkins/jobs/test/workspace
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Declarative: Tool Install)
[Pipeline] tool
$ /var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/Node_6.x/bin/npm install -g webpack webpack-dev-server phantomjs
npm WARN deprecated phantomjs@2.1.7: Package renamed to phantomjs-prebuilt. Please update 'phantomjs' package references to 'phantomjs-prebuilt'
...CUTTED
[Pipeline] envVarsForTool
[Pipeline] }
[Pipeline] // stage
[Pipeline] withEnv
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Example)
[Pipeline] sh
[workspace] Running shell script
+ npm --version
3.10.3
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
Finished: SUCCESS
In the case of JENKINS-26583 and you do not want build plugin yourself or you do not want uninstall EnvInject Plugin than the correct way (the same suggested for jdk tool as reported by cloudbees) should be:
node {
env.NODE_HOME="${tool 'Node 6.x'}"
env.PATH="${env.NODE_HOME}/bin:${env.PATH}"
sh 'npm -version'
}
Jenkins / JENKINS-43066
With pipeline, tools does not setup properly the environment
Change By:
Nikolas Falco
Status:
Open Closed
Resolution:
Fixed
[JIRA] (JENKINS-43066) With pipeline, tools does not setup properly the environment
Title: Message Title Nikolas Falco commented on JENKINS-43066 Re: With pipeline, tools does not setup properly the environment Please report also the version of plugin in the issue. This sound like duplicate of one of these JENKINS-27170 JENKINS-41762 JENKINS-42323 JENKINS-41857 JENKINS-43066 Do you have EnvInject plugin installed? If yes than you fall in JENKINS-26583 Workaround is remove EnvInject plugin, or make a custom build of workaround-26583 branch. (this branch will never merge into master, it's a EnvInject plugin issue not nodejs) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43102) Incorrect identification of arm binary at nodejs.org
Title: Message Title Nikolas Falco commented on JENKINS-43102 Re: Incorrect identification of arm binary at nodejs.org The only supported platform are linux, windows and osx (i386). No arm platform are supported. I've try to support them in the past but the main cause of failure is that there is no way to get the proper architecture, no java property has something can be use to understand which arm6/7/64 is. And due to difference beetween linux distribution I could not try to understand it using some kind of file in the system. So maybe I have to close this issue as "Won't fix" Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43109) Add "Off Switch" to octane integration
Title: Message Title Yafim Kazak updated an issue Jenkins / JENKINS-43109 Add "Off Switch" to octane integration Change By: Yafim Kazak Labels: octane Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43110) Epic for August 2017 HPE Jenkins plugin release
Title: Message Title Yafim Kazak created an issue Jenkins / JENKINS-43110 Epic for August 2017 HPE Jenkins plugin release Issue Type: Epic Assignee: Tal Abramovich Components: hp-application-automation-tools-plugin Created: 2017/Mar/26 2:24 PM Labels: hp-application-automation-tools Priority: Major Reporter: Yafim Kazak Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-43108) Upgrade mqm-rest-client dependency
Title: Message Title Yafim Kazak updated an issue Jenkins / JENKINS-43108 Upgrade mqm-rest-client dependency Change By: Yafim Kazak Labels: versioning octane Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43109) Add "Off Switch" to octane integration
Title: Message Title Michael Seldin commented on JENKINS-43109 Re: Add "Off Switch" to octane integration This issue will solve the problem for users that are not using octane integration Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43109) Add "Off Switch" to octane integration
Title: Message Title Michael Seldin assigned an issue to Michael Seldin Jenkins / JENKINS-43109 Add "Off Switch" to octane integration Change By: Michael Seldin Assignee: Ofir Shaked Michael Seldin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43109) Add "Off Switch" to octane integration
Title: Message Title Michael Seldin created an issue Jenkins / JENKINS-43109 Add "Off Switch" to octane integration Issue Type: Improvement Assignee: Ofir Shaked Components: hp-application-automation-tools-plugin Created: 2017/Mar/26 1:55 PM Priority: Critical Reporter: Michael Seldin Octane integration will not run if not configured. Partly solves issue 42855 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-43108) Upgrade mqm-rest-client dependency
Title: Message Title Michael Seldin created an issue Jenkins / JENKINS-43108 Upgrade mqm-rest-client dependency Issue Type: Improvement Assignee: Michael Seldin Components: hp-application-automation-tools-plugin Created: 2017/Mar/26 1:52 PM Labels: versioning Priority: Blocker Reporter: Michael Seldin Update dependency to mqm-rest-client ** version 1.2 new apis added: getTests deleteTests Add Comment
[JIRA] (JENKINS-43107) Blue Ocean console output, only outputs plain text
Title: Message Title yacoub hossain created an issue Jenkins / JENKINS-43107 Blue Ocean console output, only outputs plain text Issue Type: Improvement Assignee: Unassigned Components: blueocean-plugin Created: 2017/Mar/26 11:57 AM Priority: Major Reporter: yacoub hossain When using Blue Ocean UI, the console output is just plain text, wheras the classic UI had the option of plain text but by default showed a smarter console output that would, for instance, contain clickable url links to downstream jobs, or archived artifacts. That would be a very cool thing to have again in the Blue Ocean UI. Add Comment
[JIRA] (JENKINS-42947) Bitbucket-branch-source plugin does not support GIT submodules
Title: Message Title Jordan Coll commented on JENKINS-42947 Re: Bitbucket-branch-source plugin does not support GIT submodules I think this issue should be generalized for all advanced SCM behavior (clean/wipe workspace, reference repos, shallow clone, etc.) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42643) Conditional application of triggers in Declarative
Title: Message Title
Bruce Adams commented on JENKINS-42643
Re: Conditional application of triggers in Declarative
An approach that works and seems legible:
String cron_string = BRANCH_NAME == "master" ? "@hourly" : ""
pipeline {
agent none
triggers { cron(cron_string) }
stages {
// do something
}
}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43106) pipeline job hangs sporadically at checkout GitSCM
Title: Message Title
Lev Tartakovsky created an issue
Jenkins / JENKINS-43106
pipeline job hangs sporadically at checkout GitSCM
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
config.xml, Jenkinsfile, threadDump.txt
Components:
pipeline, scm-api-plugin
Created:
2017/Mar/26 9:44 AM
Environment:
OS: Ubunty 16.04 Java: openjdk version "1.8.0_121" git: 2.7.4 Jenkins: 2.32.3 (Master and slave running at the same server) Plugins: Git Client plugin: 2.4.0 Git plugin: 3.1.0 Pipeline: 2.5 Pipeline SCM Step: 2.4 SCM API Plugin: 2.1.1
Priority:
Blocker
Reporter:
Lev Tartakovsky
My pipeline job is getting sporadically hung on checkout step. Our git repo is relatively small and clone should not take more than 1 min. The problem occurring really often once a couple builds. Once it's occurring, the only way that I know to get rid of this state so far is, is disconnect the slave and re-connect it back. Build log: Started by user Checking out git to read Jenkinsfile.bootstrap > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url # timeout=10 Fetching upstream changes from > git --version # timeout=10 using GIT_SSH to set credentials jenkinsslave SSH key > git fetch --tags --progress +refs/heads/:refs/remotes/origin/ > git rev-parse refs/remotes/origin/devops_jenkins^{commit} # timeout=10 > git rev-parse refs/remotes/origin/origin/devops_jenkins^{commit} # timeout=10 Checking out Revision 2fd998fbe8b23f814b57d8c6eb7b46004268eedc (refs/remotes/origin/devops_jenkins) > git config core.sparse
