[JIRA] (JENKINS-41165) Ignore parent changes not working since v0.7.7
Title: Message Title Arno Moonen commented on JENKINS-41165 Re: Ignore parent changes not working since v0.7.7 That would be great. Thanks! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41165) Ignore parent changes not working since v0.7.7
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41165 Re: Ignore parent changes not working since v0.7.7 Code changed in jenkins User: Joseph Path: src/main/java/hudson/plugins/accurev/AccurevPromoteTrigger.java src/main/java/hudson/plugins/accurev/AccurevSCM.java src/main/java/hudson/plugins/accurev/CheckForChanges.java src/main/java/hudson/plugins/accurev/cmd/ShowStreams.java src/main/java/hudson/plugins/accurev/delegates/AbstractModeDelegate.java src/main/java/hudson/plugins/accurev/delegates/StreamDelegate.java src/main/java/hudson/plugins/accurev/delegates/WorkspaceDelegate.java http://jenkins-ci.org/commit/accurev-plugin/0efd3960d53704ee6f60ac950119baa80e5a45f7 Log: JENKINS-41165 Fix for Ignore Parent (#39) Fixing Ignore Parent Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40364) Support npm configuration file
Title: Message Title Dominik Bartholdi commented on JENKINS-40364 Re: Support npm configuration file Nikolas Falco do you need an help form my site? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41202) Managed Configuration Files cannot be saved or used
Title: Message Title Dominik Bartholdi commented on JENKINS-41202 Re: Managed Configuration Files cannot be saved or used I would say this is a bug in the openstack-plugin, but I'm quite sure Oliver Gondža already fixed this Caused by: java.lang.IllegalStateException: class org.jenkinsci.lib.configprovider.model.Config must override 'getDescriptor()' this method! at org.jenkinsci.lib.configprovider.model.Config.getDescriptor(Config.java:108) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37289) authentication issue instant is too old or in the future
Title: Message Title Jakub Bujny reopened an issue Exception still occurs on our Jenkins server, even when I incremented value to 864000 Jenkins / JENKINS-37289 authentication issue instant is too old or in the future Change By: Jakub Bujny Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more
[JIRA] (JENKINS-41202) Managed Configuration Files cannot be saved
Title: Message Title Jami Lindh created an issue Jenkins / JENKINS-41202 Managed Configuration Files cannot be saved Issue Type: Bug Assignee: Dominik Bartholdi Components: config-file-provider-plugin, openstack-cloud-plugin Created: 2017/Jan/19 7:30 AM Environment: jenkins 2.32.1 config-file-provider-plugin 2.15.4 openstack-cloud-plugin 2.17 Priority: Major Reporter: Jami Lindh After upgrading to config-file-provider-plugin v. 2.15.4 I am unable to add any configuration files to Jenkins >> Manage Jenkins >> Managed Files. The configuration file I was originally trying to create is OpenStack User Data, but the bug can be replicated with, for example, Json file. Even though I do not get any error message from config-file-provider-plugin after trying to create a configuration, openstack-cloud-plugin doesn't find any saved OpenStack User Data files when configuring cloud instances in Jenkins >> Manage Jenkins >> Configure System >> Cloud >> Templates. This bug in either of the plugins (I'm not sure which) currently renders OpenStack slaves unusable. Symptoms: When creating a new config file and saving it, no error message is given (except in system logs) but the created file does not appear in the Config File Management view and openstack-cloud-plugin can not find any configurations. Relevant logs: Opening Managed Files view Jan 19, 2017 9:16:59 AM WARNING hudson.ExpressionFactory2$JexlExpression
[JIRA] (JENKINS-41202) Managed Configuration Files cannot be saved or used
Title: Message Title Jami Lindh updated an issue Jenkins / JENKINS-41202 Managed Configuration Files cannot be saved or used Change By: Jami Lindh Summary: Managed Configuration Files cannot be saved or used Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41201) Exception with Creating Jenkins job with Customized Template using python-jenkins API
Title: Message Title
JayaBabu Animineni created an issue
Jenkins / JENKINS-41201
Exception with Creating Jenkins job with Customized Template using python-jenkins API
Issue Type:
Bug
Assignee:
Jan Niklas Hasse
Components:
python-plugin
Created:
2017/Jan/19 7:28 AM
Priority:
Minor
Reporter:
JayaBabu Animineni
Exception with Creating Jenkins job with Customized Template using python-jenkins API -- Python Code for to create jenkins Job --- import jenkins server = jenkins.Jenkins('http://:8080', username='admin', password='admin',timeout=1000) job = server.create_job(name="HelloWorld", config_xml='Template.xml') print( job) Exception --- C:\Users\SRI_14\AppData\Local\Programs\Python\Python36\python.exe "D:/MyWorkspace/Python Workspace/HelloWorld/Test.py" Traceback (most recent call last): File "C:\Users\SRI_14\AppData\Local\Programs\Python\Python36\lib\site-packages\jenkins_init_.py", line 431, in jenkins_open response = urlopen(req, timeout=self.timeout).read() File "C:\Users\SRI_14\AppData\Local\Programs\Python\Python36\lib\urllib\request.py", line 223, in urlopen return opener.open(url, data, timeout) File "C:\Users\SRI_14\AppData\Local\Programs\Python\Python36\lib\urllib\request.py", line 532, in open response = meth(req, response) File "C:\Users\SRI_14\AppData\Local\Programs\Python\Python36\lib\urllib\request.py", line 642, in http_response 'http', request, response, code, msg, hdrs) File "C:\Users\SRI_14\AppData\Local\Programs\Python\Python36\lib\urllib\request.py", line 570, in error return self._call_chain(*args) File "C:\Users\SRI_14\AppData\Local\Programs\Python\Python36\lib\urllib\request.py", line 504, in _call_chain result = func(*args) File "C:\Users\SRI_14\AppData\Local\Programs\Python\Python36\lib\urllib\request.py", line
[JIRA] (JENKINS-30700) Make Cobertura plug-in support the workflow plugin
Title: Message Title Aravind Krishna commented on JENKINS-30700 Re: Make Cobertura plug-in support the workflow plugin Yibin Sheng Thanks. However, "keepAll" just archives the reports of all previous builds, but doesn't help plot the trend report. I am wondering if there is any way to specify HTML report to plot the trend for a custom field (example: line coverage), basically what the Cobertura report publishing does. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41059) Exception in thread "LittleProxy-JVM-shutdown-hook" java.lang.NoClassDefFoundError
Title: Message Title sébastien glon commented on JENKINS-41059 Re: Exception in thread "LittleProxy-JVM-shutdown-hook" java.lang.NoClassDefFoundError I have create PR on github #42 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41059) Exception in thread "LittleProxy-JVM-shutdown-hook" java.lang.NoClassDefFoundError
Title: Message Title sébastien glon edited a comment on JENKINS-41059 Re: Exception in thread "LittleProxy-JVM-shutdown-hook" java.lang.NoClassDefFoundError I have create [ PR on github #42 |https://github.com/JFrogDev/jenkins-artifactory-plugin/pull/42] Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41165) Ignore parent changes not working since v0.7.7
Title: Message Title Joseph Petersen commented on JENKINS-41165 Re: Ignore parent changes not working since v0.7.7 I'll get it out asap then. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41165) Ignore parent changes not working since v0.7.7
Title: Message Title Joseph Petersen commented on JENKINS-41165 Re: Ignore parent changes not working since v0.7.7 Started on 19-01-2017 08:17:00 No workspace required. Running commands from folder "C:\Jenkins\jobs\accurev-plugin" Authenticating with Accurev server... [accurev-plugin] $ "C:\Program Files\AccuRev\bin\accurev.exe" login -H sandbox:5050 bam Authentication completed successfully. ... expanded '$stream' to 'steammy'. [accurev-plugin] $ "C:\Program Files\AccuRev\bin\accurev.exe" show -H sandbox:5050 -fx -p potter -s steammy streams Checking transactions of type chstream, defcomp, mkstream, promote in stream [steammy] [accurev-plugin] $ "C:\Program Files\AccuRev\bin\accurev.exe" hist -H sandbox:5050 -fx -p potter -s steammy -t now.1 -k chstream No transactions of type [chstream] [accurev-plugin] $ "C:\Program Files\AccuRev\bin\accurev.exe" hist -H sandbox:5050 -fx -p potter -s steammy -t now.1 -k defcomp Last transaction of type [defcomp] is [id=225, date=Fri Feb 06 11:32:58 CET 2015, author=dreamy, action="" msg=] [accurev-plugin] $ "C:\Program Files\AccuRev\bin\accurev.exe" hist -H sandbox:5050 -fx -p potter -s steammy -t now.1 -k mkstream Last transaction of type [mkstream] is [id=217, date=Fri Feb 06 11:29:20 CET 2015, author=dreamy, action="" msg=] [accurev-plugin] $ "C:\Program Files\AccuRev\bin\accurev.exe" hist -H sandbox:5050 -fx -p potter -s steammy -t now.1 -k promote Last transaction of type [promote] is [id=17351, date=Thu Jan 19 08:08:19 CET 2017, author=dreamy, action="" msg=pokeybear] Last valid trans [id=17351, date=Thu Jan 19 08:08:19 CET 2017, author=dreamy, action="" msg=pokeybear] Done. Took 0,7 sec Changes found Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-41165) Ignore parent changes not working since v0.7.7
Title: Message Title Arno Moonen commented on JENKINS-41165 Re: Ignore parent changes not working since v0.7.7 I just checked it and polling no longer results in an error when the snapshot version is installed. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41165) Ignore parent changes not working since v0.7.7
Title: Message Title Joseph Petersen edited a comment on JENKINS-41165 Re: Ignore parent changes not working since v0.7.7 I checked it, so far it works without variable reference edit: NVMMy workspace was on the parent stream to the one I was testing :DSo yes it works. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41200) ANSI colour support for console view
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-41200 ANSI colour support for console view Issue Type: Improvement Assignee: Unassigned Components: blueocean-plugin Created: 2017/Jan/19 7:16 AM Priority: Minor Reporter: Michael Neale Has been requested that support for ANSI colours is desired http://bitmote.com/index.php?post/2012/11/19/Using-ANSI-Color-Codes-to-Colorize-Your-Bash-Prompt-on-Linux Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-35096) Add support for Jenkins Pipeline to the cppcheck-plugin
Title: Message Title Marten Lootsma commented on JENKINS-35096 Re: Add support for Jenkins Pipeline to the cppcheck-plugin Simon Schneider I would love to try your experimental plugin. Any known issues? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41165) Ignore parent changes not working since v0.7.7
Title: Message Title Joseph Petersen commented on JENKINS-41165 Re: Ignore parent changes not working since v0.7.7 I checked it, so far it works without variable reference Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41165) Ignore parent changes not working since v0.7.7
Title: Message Title Arno Moonen commented on JENKINS-41165 Re: Ignore parent changes not working since v0.7.7 It is not a variable reference stream in our case, just a normal one. I will try to look at your changes and try it out today or tomorrow. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35836) Steps outside a stage or within a stage but outside a parallel do not get visualized
Title: Message Title James Dumay commented on JENKINS-35836 Re: Steps outside a stage or within a stage but outside a parallel do not get visualized Julien Pivotto we were discussing warnings today. Stay tuned! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35836) Steps outside a stage or within a stage but outside a parallel do not get visualized
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-35836 Steps outside a stage or within a stage but outside a parallel do not get visualized Change By: James Dumay Sprint: 1.0-japan-m9, 1.0-m7 , post-release Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41161) Config files not being updated
Title: Message Title José Roberto García Chico commented on JENKINS-41161 Re: Config files not being updated This one is also happening to me with the version 2.15.4. So waiting for the new release. Thank you! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35836) Steps outside a stage or within a stage but outside a parallel do not get visualized
Title: Message Title Julien Pivotto edited a comment on JENKINS-35836 Re: Steps outside a stage or within a stage but outside a parallel do not get visualized [~jamesdumay] This is pretty bad. I think as an immepdate immediate action we could at least print a warning when some steps are not displayed -- because that will confuse lots of users:«Warning! This pipeline contains steps that can not be displayed in Blue Ocean. Please go to [classic UI] to see all the steps. Read more in [JENKINS-35836].»[JENKINS-35836] is a link to this,[classic UI] is a link to the build "pipeline steps" view. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35836) Steps outside a stage or within a stage but outside a parallel do not get visualized
Title: Message Title Julien Pivotto commented on JENKINS-35836 Re: Steps outside a stage or within a stage but outside a parallel do not get visualized James Dumay This is pretty bad. I think as an immepdate action we could at least print a warning when some steps are not displayed – because that will confuse lots of users: «Warning! This pipeline contains steps that can not be displayed in Blue Ocean. Please go to [classic UI] to see all the steps. Read more in JENKINS-35836.» JENKINS-35836 is a link to this, [classic UI] is a link to the build "pipeline steps" view. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26653) Build Pipeline Dashboard fails with ServletException: No page found 'noJob.jelly'
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-26653 Re: Build Pipeline Dashboard fails with ServletException: No page found 'noJob.jelly' Latest version of Build Pipeline Plugin 1.5.6 still breaks for Build Pipeline Dashboard View portlets. The stacktrace is a bit different though: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/tmp/Jenkins/plugins/build-pipeline-plugin/WEB-INF/lib/build-pipeline-plugin.jar!/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView/bpp.jelly:167:32: No page found 'projectCardTemplate.jelly' for class au.com.centrumsystems.hudson.plugin.buildpipeline.extension.SimpleRowHeader Full stacktrace is attached to this issue: stacktrace-1.5.6.txt Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26653) Build Pipeline Dashboard fails with ServletException: No page found 'noJob.jelly'
Title: Message Title Allan BURDAJEWICZ updated an issue Jenkins / JENKINS-26653 Build Pipeline Dashboard fails with ServletException: No page found 'noJob.jelly' Change By: Allan BURDAJEWICZ Attachment: stacktrace-1.5.6.txt Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40986) Extend Declarative Pipeline so that it has the matrix capability
Title: Message Title
James Dumay commented on JENKINS-40986
Re: Extend Declarative Pipeline so that it has the matrix capability
Arthur Lutz would something like this solve the matrix capability you are looking for?
pipeline {
stages {
stage(‘browser tests’) {
matrix {
variants {
variant (‘firefox’) {
agent { node “linux+firefox” }
environment { key: value }
}
variant ('chrome') {
agent { node 'linux+chrome' }
environment { key: value }
}
}
environment { … }
stages { … }
}
}
}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41194) Subprojects appeared as "Unresolved" if the "projects to build" is a pipeline job.
Title: Message Title Peter Han commented on JENKINS-41194 Re: Subprojects appeared as "Unresolved" if the "projects to build" is a pipeline job. On Jenkins 1.596.1, old fashion pipeline - workflow job has the same issue. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41199) Provisioned agent ECS Slave ecs-quitest failed to launch
Title: Message Title Dennis Tran created an issue Jenkins / JENKINS-41199 Provisioned agent ECS Slave ecs-quitest failed to launch Issue Type: Story Assignee: Unassigned Attachments: Capture.PNG Components: plugin-usage-plugin Created: 2017/Jan/19 4:10 AM Environment: Jenkins 2.32.1 ECS Agent 1.13.1 Labels: jenkins ecs Priority: Minor Reporter: Dennis Tran Hi support I'm using ECS for Jenkins slave, when I build test, I saw tasks running in ECS, but in Jenkins said ECS offline. The connection between jenkins and ECS is ok, please advise me how to figure out this issue. Thanks. -- Making ecs-cloud-14121d927e9f offline because it's not responding Jan 19, 2017 3:38:36 AM WARNING hudson.node_monitors.ResponseTimeMonitor$1 monitor Making ecs-cloud-3421ccae4c82 offline because it's not responding Jan 19, 2017 3:38:46 AM WARNING hudson.model.listeners.ItemListener forAll failed to send event to listener of class org.jenkinsci.plugins.pipeline.milestone.MilestoneStepExecution$CleanupJobsOnDelete java.lang.NullPointerException at org.jenkinsci.plugins.pipeline.milestone.MilestoneStepExecution$CleanupJobsOnDelete.onDeleted(MilestoneStepExecution.java:348) at hudson.model.listeners.ItemListener$4.apply(ItemListener.java:205) at hudson.model.listeners.ItemListener$4.apply(ItemListener.java:203) at
[JIRA] (JENKINS-38578) Git Publisher is not working after promotion of build
Title: Message Title
Maneesh Mehra edited a comment on JENKINS-38578
Re: Git Publisher is not working after promotion of build
I ran into this issue as well. Here are the steps to reproduce the problem:0. Install the Git plugin along with the Jenkins Promoted Builds plugin. In my case, I had the following versions installed: - Git Plugin (https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin) v3.0.3 - Promoted Builds Plugin (https://wiki.jenkins-ci.org/display/JENKINS/Promoted+Builds+Plugin) v2.28 1. Create a freestyle Jenkins job. 2. Configure the job and add a link to a git repository. In my case, I integrated my Jenkins environment against a Gitlab CE server and used that. 3. Test connection to the Git remote repository to ensure connectivity and access. 4. Check the "Promote builds when..." checkbox under "General" section. 4.1 Give a descriptive name to the promotion. 4.2 Add an action for "Git Publisher". 4.3. Within the Git Publisher action, select the "Push Only If Build Succeeds" checkbox. Add the option to push a new tag to the repository by providing a tag token of the form: JENKINS_${BUILD_ID}, a tag message and the checkbox to "create new tag". 5. Save the Jenkins build job. 6. Run the job. Since we did not any build steps to the job, as long as Jenkins is able to clone the Git repo successfully, the job will be successful. 7. On the job results page, click the "Promotion Status" link. 8. Press the box which says "Force Promotion" or "Re-execute Promotion". The former will be available for a new job that has never been promoted or attempted to be promoted. The latter will be available for previously promoted/attempted to be promoted jobs. 9. Notice that the promotion job will now run and its console will present something like the following as the error message:build hudson.tasks.Shell@61a99866 SUCCESSfailed build hudson.plugins.git.GitPublisher@11fd2de1 SUCCESSFinished: FAILUREI debugged the Git plugin upto a certain point and noticed that that on line 184 (in version 3.0.3 of source code this was SCM scm = build.getProject().getScm()), scm's value was NullSCM. I am suspecting that since the promotion job is run separately from the main Jenkins job, Jenkins is not providing any knowledge of the SCM system (git) to the promotion job. I am not particularly familiar with how the promotion jobs run and so unable to tell why the SCM value was not set when the execution hits this portion of the code.I hope this helps debug the issue a bit more.Thanks,Maneesh
Add Comment
[JIRA] (JENKINS-38578) Git Publisher is not working after promotion of build
Title: Message Title
Maneesh Mehra commented on JENKINS-38578
Re: Git Publisher is not working after promotion of build
I ran into this issue as well. Here are the steps to reproduce the problem: 0. Install the Git plugin along with the Jenkins Promoted Builds plugin. In my case, I had the following versions installed:
Git Plugin (https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin) v3.0.3
Promoted Builds Plugin (https://wiki.jenkins-ci.org/display/JENKINS/Promoted+Builds+Plugin) v2.28 1. Create a freestyle Jenkins job. 2. Configure the job and add a link to a git repository. In my case, I integrated my Jenkins environment against a Gitlab CE server and used that. 3. Test connection to the Git remote repository to ensure connectivity and access. 4. Check the "Promote builds when..." checkbox under "General" section. 4.1 Give a descriptive name to the promotion. 4.2 Add an action for "Git Publisher". 4.3. Within the Git Publisher action, select the "Push Only If Build Succeeds" checkbox. Add the option to push a new tag to the repository by providing a tag token of the form: JENKINS_$ {BUILD_ID} , a tag message and the checkbox to "create new tag". 5. Save the Jenkins build job. 6. Run the job. Since we did not any build steps to the job, as long as Jenkins is able to clone the Git repo successfully, the job will be successful. 7. On the job results page, click the "Promotion Status" link. 8. Press the box which says "Force Promotion" or "Re-execute Promotion". The former will be available for a new job that has never been promoted or attempted to be promoted. The latter will be available for previously promoted/attempted to be promoted jobs. 9. Notice that the promotion job will now run and its console will present something like the following as the error message:
build hudson.tasks.Shell@61a99866 SUCCESS failed build hudson.plugins.git.GitPublisher@11fd2de1 SUCCESS Finished: FAILURE I debugged the Git plugin upto a certain point and noticed that that on line 184 (in version 3.0.3 of source code this was SCM scm = build.getProject().getScm()), scm's value was NullSCM. I am suspecting that since the promotion job is run separately from the main Jenkins job, Jenkins is not providing any knowledge of the SCM system (git) to the promotion job. I am not particularly familiar with how the promotion jobs run and so unable to tell why the SCM value was not set when the execution hits this portion of the code. I hope this helps debug the issue a bit more. Thanks, Maneesh
Add Comment
[JIRA] (JENKINS-39792) When there are no branches the user should be promoted to create a Jenkinsfile on a new branch
Title: Message Title Brody Maclean assigned an issue to James Dumay Jenkins / JENKINS-39792 When there are no branches the user should be promoted to create a Jenkinsfile on a new branch Change By: Brody Maclean Assignee: Brody Maclean James Dumay Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41198) per parallel agent configuration
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-41198 per parallel agent configuration Issue Type: Improvement Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2017/Jan/19 3:36 AM Priority: Major Reporter: Michael Neale Given a large use of parallel is to run chunks of steps on different agents, it may make sense to allow agent to be configured in a parallel branch vs only at the parent stage level. Currently parallel lives at the steps level, so this likely could be a disruptive change (maybe not). Currently to use distributed builds in parallel vs sequential means dropping in to using the node syntax (and excludes usage of things like docker inside), which is a bit of a disjointed experience. Add Comment
[JIRA] (JENKINS-41198) Per parallel branch agent configuration
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-41198 Per parallel branch agent configuration Change By: Michael Neale Summary: per Per parallel branch agent configuration Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41121) GitHub Branch Source upgrade can cause a lot of rebuilds
Title: Message Title Michael Neale commented on JENKINS-41121 Re: GitHub Branch Source upgrade can cause a lot of rebuilds FYI Ben Walding also saw this on a private instance with a large number of jobs and branches. All the branches retriggered automatically (he doesn't use PRs) with no code change. This could have been much worse as some branches represent deployments (and whilst it would deploy the same thing.. one does not simply redeploy for fun - and he has other gates in place that make it a non issue but it may be surprising behavior to many). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41121) GitHub Branch Source upgrade can cause a lot of rebuilds
Title: Message Title Michael Neale edited a comment on JENKINS-41121 Re: GitHub Branch Source upgrade can cause a lot of rebuilds FYI [~bwalding] also saw this on a private instance with a large number of jobs and branches. All the branches retriggered automatically (he doesn't use PRs) with no code change. This could have been much worse as some branches represent deployments (and whilst it would deploy the same thing.. one does not simply redeploy for fun - and he has other gates in place that make it a non issue but it may be surprising behavior to many). This was using a mutlibranch github project. Not org folder. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39792) When there are no branches the user should be promoted to create a Jenkinsfile on a new branch
Title: Message Title Brody Maclean commented on JENKINS-39792 Re: When there are no branches the user should be promoted to create a Jenkinsfile on a new branch Zeplin https://zpl.io/15eMCT Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39792) When there are no branches the user should be promoted to create a Jenkinsfile on a new branch
Title: Message Title Brody Maclean updated an issue Jenkins / JENKINS-39792 When there are no branches the user should be promoted to create a Jenkinsfile on a new branch Change By: Brody Maclean Attachment: Branches Empty.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27039) Option for input or stage step to cancel older executions
Title: Message Title Michael Neale reopened an issue Re-opening as neither myself or anyone I know has observed this behavior. This may be a bug vs a feature request. To reproduce: open a PR, let it start building, push an update to the PR, note that there will be 2 concurrent pipeline runs. Jenkins / JENKINS-27039 Option for input or stage step to cancel older executions Change By: Michael Neale Resolution: Fixed Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins
[JIRA] (JENKINS-27039) Option for input or stage step to cancel older executions
Title: Message Title Michael Neale commented on JENKINS-27039 Re: Option for input or stage step to cancel older executions Alexander Uvizhev ah I understand you now. I am not sure of an out of the box way to do that. Maybe some plugin contributes that functionality and it does seem like a nice to have feature. It would be possible to script so that when a job starts, if it nows it is a PR, it looks in the history for older running ones and cancels them, but that may be a tad extreme. But possible. Crazier things have been done. It would be nice if this was just a config option of course, I agree. I never care about older runs of a PR fork or branch. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40810) UnsupportedClassVersionError when using JDK6
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40810 Re: UnsupportedClassVersionError when using JDK6 Code changed in jenkins User: Daniel Beck Path: content/changelog-stable/index.html content/doc/upgrade-guide/2.32.adoc http://jenkins-ci.org/commit/jenkins.io/1692ba554089a4281a8407372a51af5c3ef19db6 Log: JENKINS-40810 Mention effect of Remoting 3 on Maven builds Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40810) UnsupportedClassVersionError when using JDK6
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40810 Re: UnsupportedClassVersionError when using JDK6 Code changed in jenkins User: Daniel Beck Path: content/changelog-stable/index.html http://jenkins-ci.org/commit/jenkins.io/39718b18cb7c201a6ce6d37b541e7736c3b8fc2b Log: JENKINS-40810 Make Java requirement explicit Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40810) UnsupportedClassVersionError when using JDK6
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40810 Re: UnsupportedClassVersionError when using JDK6 Code changed in jenkins User: R. Tyler Croy Path: content/changelog-stable/index.html content/doc/upgrade-guide/2.32.adoc http://jenkins-ci.org/commit/jenkins.io/7dc33503c5af2c7be284927e78ca2d3c9870761b Log: Merge pull request #554 from daniel-beck/JENKINS-40810 JENKINS-40810 Mention effect of Remoting 3 on Maven builds Compare: https://github.com/jenkins-infra/jenkins.io/compare/294071086e58...7dc33503c5af Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41129) Ivy plugin throws NPE if no project settings defined
Title: Message Title Kevin Formsma resolved as Fixed Fixed with 1.27.1 Thanks for the PR! Jenkins / JENKINS-41129 Ivy plugin throws NPE if no project settings defined Change By: Kevin Formsma Status: Open Resolved Assignee: Timothy Bingaman Kevin Formsma Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are
[JIRA] (JENKINS-41129) Ivy plugin throws NPE if no project settings defined
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41129 Re: Ivy plugin throws NPE if no project settings defined Code changed in jenkins User: Kevin Formsma Path: src/main/java/hudson/ivy/IvyModuleSetBuild.java http://jenkins-ci.org/commit/ivy-plugin/6c3b575b2e9a9da55cfafe36b98da0391c6a4f68 Log: Merge pull request #24 from jamieps/issue/project-settings-npe JENKINS-41129 Prevent null pointer dereference Compare: https://github.com/jenkinsci/ivy-plugin/compare/9dea269ec058...6c3b575b2e9a Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41129) Ivy plugin throws NPE if no project settings defined
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41129 Re: Ivy plugin throws NPE if no project settings defined Code changed in jenkins User: Jamie L. Penman-Smithson Path: src/main/java/hudson/ivy/IvyModuleSetBuild.java http://jenkins-ci.org/commit/ivy-plugin/0859a584a54c7bfac16baf82674953f112b74a8c Log: JENKINS-41129 Prevent null pointer dereference if project has no settings defined. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41197) [Pipeline] Pipeline step to exit the build immediately as a success
Title: Message Title Sean Sutherland created an issue Jenkins / JENKINS-41197 [Pipeline] Pipeline step to exit the build immediately as a success Issue Type: New Feature Assignee: Unassigned Components: workflow-basic-steps-plugin Created: 2017/Jan/19 2:01 AM Priority: Minor Reporter: Sean Sutherland It would be convenient if there was a pipeline step that would exit the run immediately, but not have it be necessarily be a failure. This would be useful in situations where a run determines it no longer has work to do, and so it should end immediately as success (or whatever the current result state is). If we have multiple such decision points in a build, doing this with conditionals gets incredibly messy quite quickly. Add Comment
[JIRA] (JENKINS-41196) Pluggable core component
Title: Message Title Kohsuke Kawaguchi created an issue Jenkins / JENKINS-41196 Pluggable core component Issue Type: Improvement Assignee: Unassigned Components: core Created: 2017/Jan/19 1:55 AM Priority: Major Reporter: Kohsuke Kawaguchi Problems There are quite a few libraries that core bundles. Some of them, such as remoting, stapler, and so on, are heavily used by plugins and systems we build on top of Jenkins core, such as Blue Ocean. This situation creates a class of pain for those plugins; when they need a newer feature or a bug fix in those libraries, they have to wait for multiple months before the change propagates to a version of LTS. Solution If we can modify Jenkins core such that it allows any of its libraries to be shipped as plugins, then this would eliminate this class of pain altogether. Add Comment
[JIRA] (JENKINS-41196) Pluggable core component
Title: Message Title Kohsuke Kawaguchi commented on JENKINS-41196 Re: Pluggable core component For my internal tracking purpose, the original document is here Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41195) Managed script visualisation
Title: Message Title Grigoriy Milman updated an issue Jenkins / JENKINS-41195 Managed script visualisation Change By: Grigoriy Milman Jenkins was upgraded from 1.644 TO 2.40Managed Scripts plugin was upgraded to 1.3During job config creation the following was found: Two Windows batch scripts have been set up to for execution during Build step (see attached [^ManagedPluginIssue.PNG]) * first named "Prepare Target only";* second named "Release note in Target"1. The "view selected script" became visible only for the first script.2. When "view selected script" is clicked it shows the second script (see attached [^ManagedPluginIssue.PNG]) ! 3. Required arguments are not visible as before Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options,
[JIRA] (JENKINS-41195) Managed script visualisation
Title: Message Title Grigoriy Milman updated an issue Jenkins / JENKINS-41195 Managed script visualisation Change By: Grigoriy Milman Summary:
[JIRA] (JENKINS-41195)
Title: Message Title Grigoriy Milman created an issue Jenkins / JENKINS-41195 Issue Type: Bug Assignee: Dominik Bartholdi Attachments: ManagedPluginIssue.PNG Components: managed-scripts-plugin Created: 2017/Jan/19 1:31 AM Environment: Windows, Firefox as browser; Jenkins 2.40 Config File Provider Plugin 2.15.4 Managed Scripts 1.3 Priority: Major Reporter: Grigoriy Milman Jenkins was upgraded from 1.644 TO 2.40 Managed Scripts plugin was upgraded to 1.3 During job config creation the following was found: Two Windows batch scripts have been set up to during Build step (see attached ManagedPluginIssue.PNG) first named "Prepare Target only"; second named "Release note in Target" 1. The "view selected script" became visible only for the first script. 2. When "view selected script" is clicked it shows the second script (see attached ManagedPluginIssue.PNG) ! 3. Required arguments not visible as before
[JIRA] (JENKINS-35836) Steps outside a stage or within a stage but outside a parallel do not get visualized
Title: Message Title Michael Neale commented on JENKINS-35836 Re: Steps outside a stage or within a stage but outside a parallel do not get visualized I have made this one dependent on nested stages, as it seems after a closer look to be very very similar (at least the solutions will likely be similar). Ie if we can support nested stages, we can support nested synthetic stages for these post/pre parallel steps Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41047) API error message improvement
Title: Message Title Vivek Pandey updated JENKINS-41047 Jenkins / JENKINS-41047 API error message improvement Change By: Vivek Pandey Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41187) [Declarative Pipeline] Stage "when" should have "stage" condition
Title: Message Title
Liam Newman commented on JENKINS-41187
Re: [Declarative Pipeline] Stage "when" should have "stage" condition
Patrick Wolf I'm open to discussion of how it should look, but I think we need some form of this. "Right now the use case described is easily done as shown." Yes, like I said, for simple expressions things are fine, but for complex expressions this would get unwieldy very fast.
stages {
stage ('Full Build') {
when {
_expression_ {
GIT_BRANCH = 'origin/' + sh(returnStdout: true, script: 'git rev-parse --abbrev-ref HEAD').trim()
return GIT_BRANCH == 'origin/master' || params.FORCE_FULL_BUILD
}
}
}
stage ('Incremental Build') {
when {
_expression_ {
GIT_BRANCH = 'origin/' + sh(returnStdout: true, script: 'git rev-parse --abbrev-ref HEAD').trim()
return !(GIT_BRANCH == 'origin/master' || params.FORCE_FULL_BUILD)
}
}
}
}
Then repeat that condition over and over for other stages. Mediocre. I see your point about the specific `stage {}` condition syntax I described being not great, but I also don't want to use general comparison operators if we can avoid them here. Also, stages run in serial and failure in a previous stage would generally stop the pipeline right? Maybe this:
stages {
stage ('Full Build') {
when {
_expression_ { return params.FORCE_FULL_BUILD }
}
}
stage ('Incremental Build') {
when {
stages('Full Build').skipped
}
}
stage ('Full Tests') {
when {
stages('Full Build').executed
}
}
stage ('Incremental Tests') {
when {
stages('Incremental Build').executed
}
}
}
Or we could follow your status example:
stages {
stage ('Full Build') {
when {
_expression_ { return params.FORCE_FULL_BUILD }
}
}
stage ('Incremental Build') {
when {
stages('Full Build').skipped
}
}
stage ('Full Tests') {
when {
stages('Full Build').succeeded
}
}
stage ('Incremental Tests') {
when {
stages('Incremental Build').succeeded
}
}
}
[JIRA] (JENKINS-37987) Image.inside fails for images specifying ENTRYPOINT
Title: Message Title Kohsuke Kawaguchi commented on JENKINS-37987 Re: Image.inside fails for images specifying ENTRYPOINT Since Jesse is rather terse in his comment, what he really means is that the regression people reported is currently tracked as JENKINS-39748, so if you are affected by this, please follow that issue. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35836) Steps outside a stage or within a stage but outside a parallel do not get visualized
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-35836
Steps outside a stage or within a stage but outside a parallel do not get visualized
Change By:
James Dumay
{panel:title=This feature request is unplanned and is not actively being worked on|titleBGColor=lightgrey}We are unable to merge orphaned steps (that is, steps that exist outside of a stage or outside of a parallel within a stage) into the closest stage or a synthetic without considerable engineering effort to ensure that all steps are available in the visualization . As a workaround we recommend that you wrap any steps within {{stage}} and do not include steps sitting outside a {{parallel}} in the same stage.{panel}*Scope*For visualisation purposes:* Step outside stage is relocated to the previous stage or next stage (depending if at start, middle or end of the pipeline)* Step before a parallel block is relocated to the first parallel branch* Step after a parallel block is relocated to the last parallel branch*Problem*It is possible that a stage, that has parallel branches under it, also has steps before or after a parallel section. *Example 1 - step outside stage block*The output of the step that echos _never going to let you down_ will never be visible from the UI.{code}node { stage "Stage 1" {sh "echo never going to give you up" } sh "echo never going to let you down" stage "Stage 2" {parallel ( "Firefox" : { echo "Never run around" }, "Edge" : { echo "Never desert you" }) }stage "Stage 3" {echo "Make you cry (never)"echo "Tell a lie and hurt you (never)" }}{code}*Example 2 - step inside stage but not within parallel*The output of the step that echos _never going to let you down_ will never be visible from the UI.{code}node { stage "Stage 1" {sh "echo never going to give you up" }stage "Stage 2" {sh "echo never going to let you down"parallel ( "Firefox" : { echo "Never run around" }, "Edge" : { echo "Never desert you" }) }stage "Stage 3" {echo "Make you cry (never)"echo "Tell a lie and hurt you (never)" }}{code}
Add Comment
[JIRA] (JENKINS-35836) Steps outside a stage or within a stage but outside a parallel do not get visualized
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-35836
Steps outside a stage or within a stage but outside a parallel do not get visualized
Change By:
James Dumay
{panel:title=This feature request is unplanned and is not actively being worked on|titleBGColor=lightgrey}We are unable to merge orphaned steps (that is, steps that exist outside of a stage or outside of a parallel within a stage) without considerable engineering effort.As a workaround we recommend that you wrap any steps within {{stage}} and do not include steps sitting outside a {{parallel}} in the same stage.{panel} *Scope*For visualisation purposes:* Step outside stage is relocated to the previous stage or next stage (depending if at start, middle or end of the pipeline)* Step before a parallel block is relocated to the first parallel branch* Step after a parallel block is relocated to the last parallel branch*Problem*It is possible that a stage, that has parallel branches under it, also has steps before or after a parallel section. *Example 1 - step outside stage block*The output of the step that echos _never going to let you down_ will never be visible from the UI.{code}node { stage "Stage 1" {sh "echo never going to give you up" } sh "echo never going to let you down" stage "Stage 2" {parallel ( "Firefox" : { echo "Never run around" }, "Edge" : { echo "Never desert you" }) }stage "Stage 3" {echo "Make you cry (never)"echo "Tell a lie and hurt you (never)" }}{code}*Example 2 - step inside stage but not within parallel*The output of the step that echos _never going to let you down_ will never be visible from the UI.{code}node { stage "Stage 1" {sh "echo never going to give you up" }stage "Stage 2" {sh "echo never going to let you down"parallel ( "Firefox" : { echo "Never run around" }, "Edge" : { echo "Never desert you" }) }stage "Stage 3" {echo "Make you cry (never)"echo "Tell a lie and hurt you (never)" }}{code}
Add Comment
[JIRA] (JENKINS-35836) Steps outside a stage or within a stage but outside a parallel do not get visualized
Title: Message Title James Dumay assigned an issue to Unassigned Jenkins / JENKINS-35836 Steps outside a stage or within a stage but outside a parallel do not get visualized Change By: James Dumay Assignee: Vivek Pandey Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35836) Steps outside a stage or within a stage but outside a parallel do not get visualized
Title: Message Title
Michael Neale updated an issue
Jenkins / JENKINS-35836
Steps outside a stage or within a stage but outside a parallel do not get visualized
Change By:
Michael Neale
*Scope*For visualisation purposes:* Step outside stage is relocated to the previous stage or next stage (depending if at start, middle or end of the pipeline)* Step before a parallel block is relocated to the first parallel branch* Step after a parallel block is relocated to the last parallel branch*Problem*It is possible that a stage, that has parallel branches under it, also has steps before or after a parallel section. *Example 1 - step outside stage block*The output of the step that echos _never going to let you down_ will never be visible from the UI.{code} node { stage "Stage 1" {sh "echo never going to give you up" } sh "echo never going to let you down" stage "Stage 2" {parallel ( "Firefox" : { echo "Never run around" }, "Edge" : { echo "Never desert you" }) }stage "Stage 3" {echo "Make you cry (never)"echo "Tell a lie and hurt you (never)" }} {code}*Example 2 - step inside stage but not within parallel*The output of the step that echos _never going to let you down_ will never be visible from the UI.{code}node { stage "Stage 1" {sh "echo never going to give you up" }stage "Stage 2" {sh "echo never going to let you down"parallel ( "Firefox" : { echo "Never run around" }, "Edge" : { echo "Never desert you" }) }stage "Stage 3" {echo "Make you cry (never)"echo "Tell a lie and hurt you (never)" }}{code}
Add Comment
[JIRA] (JENKINS-35836) Steps outside a stage or within a stage but outside a parallel do not get visualized
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-35836 Steps outside a stage or within a stage but outside a parallel do not get visualized Change By: James Dumay Sprint: 1.0-japan-m9, 1.0-m7 , tethys Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41194) Subprojects appeared as "Unresolved" if the "projects to build" is a pipeline job.
Title: Message Title Ning Wang created an issue Jenkins / JENKINS-41194 Subprojects appeared as "Unresolved" if the "projects to build" is a pipeline job. Issue Type: Bug Assignee: huybrechts Components: parameterized-trigger-plugin Created: 2017/Jan/19 12:45 AM Environment: Jenkins 2.19.1 parameterized-trigger-plugin2.32 Priority: Major Reporter: Ning Wang Scenario: The job A launches job B by configuring "projects to build", and B is a pipeline job. Issue: Main page of job A shows: Subprojects Unresolved B Add Comment
[JIRA] (JENKINS-41165) Ignore parent changes not working since v0.7.7
Title: Message Title Joseph Petersen commented on JENKINS-41165 Re: Ignore parent changes not working since v0.7.7 Could you perhaps check the build for me? Cause I am going to be bed. https://jenkins.ci.cloudbees.com/job/plugins/job/accurev-plugin/200/org.jenkins-ci.plugins$accurev/ Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41187) [Declarative Pipeline] Stage "when" should have "stage" condition
Title: Message Title
Patrick Wolf edited a comment on JENKINS-41187
Re: [Declarative Pipeline] Stage "when" should have "stage" condition
I don't like this syntax formatting.When I see this :{code:java}stage ('Incremental Build') {when {not { stage 'Full Build' }}}{code}I read it as when this Stage is not "Full Build". My first reaction is that is always true.If we want to say it is dependent in someway then we need to make that relationship explicit. When {{stage "Full Build " }} is not what? Not skipped, not run, not stable? That isn't clear.Right now the use case described is easily done as shown. To me that is much more clear than the alternative. We can explore having some {{stage}} conditions but they need to be clear.Maybe something like:{code:java}stage ('Incremental Build') {when { stage 'Full Build' == SKIPPED}}{code}Or{code:java}stage ('Incremental Build') {when { stage 'Full Build' == SUCCESS}}{code}Or{code:java}stage ('Incremental Build') {when { stage 'Full Build' != UNSTABLE}}{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41187) [Declarative Pipeline] Stage "when" should have "stage" condition
Title: Message Title
Patrick Wolf commented on JENKINS-41187
Re: [Declarative Pipeline] Stage "when" should have "stage" condition
I don't like this syntax formatting. When I see this :
stage ('Incremental Build') {
when {
not { stage 'Full Build' }
}
}
I read it as when this Stage is not "Full Build". My first reaction is that is always true. If we want to say it is dependent in someway then we need to make that relationship explicit. When stage "Full Build is not what? Not skipped, not run, not stable? That isn't clear. Right now the use case described is easily done as shown. To me that is much more clear than the alternative. We can explore having some stage conditions but they need to be clear. Maybe something like:
stage ('Incremental Build') {
when {
stage 'Full Build' == SKIPPED
}
}
Or
stage ('Incremental Build') {
when {
stage 'Full Build' == SUCCESS
}
}
Or
stage ('Incremental Build') {
when {
stage 'Full Build' != UNSTABLE
}
}
Add Comment
[JIRA] (JENKINS-41165) Ignore parent changes not working since v0.7.7
Title: Message Title Joseph Petersen started work on JENKINS-41165 Change By: Joseph Petersen Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41193) Add log API for Org scanning and MBP indexing
Title: Message Title Vivek Pandey created an issue Jenkins / JENKINS-41193 Add log API for Org scanning and MBP indexing Issue Type: Task Assignee: Vivek Pandey Components: blueocean-plugin Created: 2017/Jan/18 11:57 PM Labels: API Priority: Major Reporter: Vivek Pandey Creation flow needs API to fetch log for organization folder scanning and multi-branch-pipeline indexing logs. cc: Cliff Meyers Add Comment
[JIRA] (JENKINS-38754) Failing test view omits important stdout/stderr information
Title: Message Title Ivan Meredith updated JENKINS-38754 Jenkins / JENKINS-38754 Failing test view omits important stdout/stderr information Change By: Ivan Meredith Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41165) Ignore parent changes not working since v0.7.7
Title: Message Title Joseph Petersen commented on JENKINS-41165 Re: Ignore parent changes not working since v0.7.7 Never mind, had some spare time right now Would this in any case be a Variable Reference stream it is trying to find? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40526) Developer would like to get the logs for a stage or parallel
Title: Message Title Brody Maclean assigned an issue to James Dumay Jenkins / JENKINS-40526 Developer would like to get the logs for a stage or parallel Change By: Brody Maclean Assignee: James Dumay Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41087) When the user wants to create classic pipelines
Title: Message Title Brody Maclean assigned an issue to James Dumay Jenkins / JENKINS-41087 When the user wants to create classic pipelines Change By: Brody Maclean Assignee: Brody Maclean James Dumay Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41087) When the user wants to create classic pipelines
Title: Message Title Brody Maclean commented on JENKINS-41087 Re: When the user wants to create classic pipelines Zeplin https://zpl.io/1PPGsB Mockup with link in header Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41087) When the user wants to create classic pipelines
Title: Message Title Brody Maclean updated an issue Jenkins / JENKINS-41087 When the user wants to create classic pipelines Change By: Brody Maclean Attachment: screenshot-1.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38754) Failing test view omits important stdout/stderr information
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38754 Re: Failing test view omits important stdout/stderr information Code changed in jenkins User: Ivan Meredith Path: src/test/js/multibranch/testResults.js src/test/resources/multibranch/test_results/TEST-io.blueocean.StdoutStderr.xml http://jenkins-ci.org/commit/blueocean-acceptance-test/32e0cda8f175dbaca0aa206a40382ede2929afb6 Log: JENKINS-38754 Add test coverage for Standoutput and standard error Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41192) Git Plugin 2.6.0 branch still has beta dependencies
Title: Message Title recampbell assigned an issue to Stephen Connolly Jenkins / JENKINS-41192 Git Plugin 2.6.0 branch still has beta dependencies Change By: recampbell Assignee: Mark Waite Stephen Connolly Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41192) Git Plugin 2.6.0 branch still has beta dependencies
Title: Message Title recampbell created an issue Jenkins / JENKINS-41192 Git Plugin 2.6.0 branch still has beta dependencies Issue Type: Task Assignee: Mark Waite Components: git-plugin Created: 2017/Jan/18 11:50 PM Priority: Major Reporter: recampbell The abandoned git-plugin 2.6.2 was actually released with beta dependencies. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-41191) read-only artifact files and build slaves
Title: Message Title
Andrew Johnson created an issue
Jenkins / JENKINS-41191
read-only artifact files and build slaves
Issue Type:
Bug
Assignee:
ikedam
Components:
copyartifact-plugin
Created:
2017/Jan/18 11:37 PM
Environment:
Jenkins 1.658 with Copy Artifact plugin 1.38.1 Master on 64-bit RHEL6, build slaves on 32-bit RHEL6, MacOS and Solaris.
Labels:
slave
Priority:
Minor
Reporter:
Andrew Johnson
If an artifact file was created read-only (i.e. with permissions rrr-) when it was archived, the copyartifact plugin installs it as read-only too, which is what I would expect. Unfortunately when the build job runs a second time, the next attempt to copy the same artifact file then fails because it's trying to overwrite a read-only file. This doesn't seem to cause a problem with builds running on the master node, but it fails on my Linux, macOS and Solaris build slaves (I'm using a multi-config job to build the same code on all 4 OSs). The console output from one such slave job is shown below. If I wipe out the workspaces on the slaves, the next build that runs will succeed. {{FATAL: Failed to copy /var/lib/jenkins/jobs/extensions-3.14-ezca/configurations/axis-OS/linux32/builds/5/archive/include/ezca.h to /local/jenkins/workspace/extensions-3.14-ezcaScan/OS/linux32/include/ezca.h hudson.util.IOException2: Failed to copy /var/lib/jenkins/jobs/extensions-3.14-ezca/configurations/axis-OS/linux32/builds/5/archive/include/ezca.h to /local/jenkins/workspace/extensions-3.14-ezcaScan/OS/linux32/include/ezca.h at
[JIRA] (JENKINS-41190) Bitbucket Cloud API Implementation uses incorrect domain names
Title: Message Title Erik van Zijst updated an issue Jenkins / JENKINS-41190 Bitbucket Cloud API Implementation uses incorrect domain names Change By: Erik van Zijst This plugin uses https://bitbucket.org/api/.. as it's base URL. This is not a valid or even supported URL on Bitbucket. It currently *happens to work*, but won't in the future.As per the documentation, Bitbucket's API lives on https://api.bitbucket.org https://developer.atlassian.com/bitbucket/api/2/reference/meta/uri-uuid#uri-structure Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41190) Bitbucket Cloud API Implementation uses incorrect domain names
Title: Message Title Erik van Zijst created an issue Jenkins / JENKINS-41190 Bitbucket Cloud API Implementation uses incorrect domain names Issue Type: Bug Assignee: Antonio Muñiz Components: bitbucket-branch-source-plugin Created: 2017/Jan/18 11:35 PM Priority: Critical Reporter: Erik van Zijst This plugin uses https://bitbucket.org/api/.. as it's base URL. This is not a valid or even supported URL on Bitbucket. It currently happens to work, but won't in the future. As per the documentation, Bitbucket's API lives on https://api.bitbucket.org https://developer.atlassian.com/bitbucket/api/2/reference/meta/uri-uuid#uri-structure Add Comment
[JIRA] (JENKINS-37351) running jobs sequentially - ordering
Title: Message Title Monkey Little commented on JENKINS-37351 Re: running jobs sequentially - ordering I'm having the same problem - current multi job plugin version is 1.23. So basically "Job execution type" parameter is not working at all. This needs to be fixed immediately - a major bug. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41189) [Pipeline] Some non-CPS transformable code will not throw errors
Title: Message Title
Sean Sutherland created an issue
Jenkins / JENKINS-41189
[Pipeline] Some non-CPS transformable code will not throw errors
Issue Type:
Bug
Assignee:
Unassigned
Components:
workflow-cps-plugin
Created:
2017/Jan/18 11:22 PM
Environment:
CloudBees Jenkins Enterprise 2.7.19.1-rolling Workflow CPS plugin 2.23
Priority:
Minor
Reporter:
Sean Sutherland
The groovy cps documentation does warn that some loop constructs are not cps transformable. However, when they are used, they will behave incorrectly (and silently) rather than throwing an error. repro case
println (["dog", "cat"].findAll{it.contains("dog")})
In a regular groovy shell, this will return ["dog"], as you would expect. In a pipeline job, this will return true.
[JIRA] (JENKINS-38820) Internal Server Error from Bitbucket when attempting to index branches
Title: Message Title Marcus Bertrand updated an issue Jenkins / JENKINS-38820 Internal Server Error from Bitbucket when attempting to index branches Change By: Marcus Bertrand Summary: Internal Server Error from BitBucket Bitbucket when attempting to index branches Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38820) Internal Server Error from BitBucket when attempting to index branches
Title: Message Title
Marcus Bertrand commented on JENKINS-38820
Re: Internal Server Error from BitBucket when attempting to index branches
Hi all, I work on the Bitbucket Cloud dev team and am working a similar sounding case with our support team. Looking at the plugin, I can see that it is still using Bitbucket Cloud's very outdated, and deprecated, 1.0 API endpoint for listing branches. The 1.0 API tries to include a diff stat with every branch, causing repositories with a lot of branches & tags (yes, and tags) to hit Bitbucket Cloud's internal timeouts for API performance. To resolve this issue, the plugin should switch to using the more modern 2.0 API for gathering branch information. The endpoint for getting branch refs is
https://api.bitbucket.org/2.0/repositories/{username}/{repo_slug}/refs/branches
Cheers, Marcus Bertrand
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41188) [Pipeline] External libraries should be able to declare dependencies
Title: Message Title Sean Sutherland commented on JENKINS-41188 Re: [Pipeline] External libraries should be able to declare dependencies One option would be to let external libraries use the @Library annotation, and thus have the dependency resolution occur at compile/run time. Alternately, libraries could define their dependencies in a data/groovy/json file in a predetermined location, and then the validation could be done statically. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41188) [Pipeline] External libraries should be able to declare dependencies
Title: Message Title Sean Sutherland created an issue Jenkins / JENKINS-41188 [Pipeline] External libraries should be able to declare dependencies Issue Type: Improvement Assignee: Unassigned Components: workflow-cps-global-lib-plugin Created: 2017/Jan/18 11:07 PM Priority: Minor Reporter: Sean Sutherland Pipeline libraries should be able to declare dependencies on other external libraries, so that the Jenkins configuration doesn't have to manage the entire version set. This would allow for safer adoption of new versions of libraries. Add Comment
[JIRA] (JENKINS-32128) Uploading to HockeyApp timed out
Title: Message Title Brantone commented on JENKINS-32128 Re: Uploading to HockeyApp timed out This still causing problems? I suspect issue with network Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23329) java.io.IOException
Title: Message Title Brantone commented on JENKINS-23329 Re: java.io.IOException This still a problem with latest versions? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24255) HockeyApp plugin doesn't upload multiple IPAs as documented
Title: Message Title Brantone closed an issue as Fixed Available in 1.0.6 Jenkins / JENKINS-24255 HockeyApp plugin doesn't upload multiple IPAs as documented Change By: Brantone Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-19636) Enable Ant style file name patterns for the .ipa and .dSYM.zip names
Title: Message Title Brantone closed an issue as Fixed Jenkins / JENKINS-19636 Enable Ant style file name patterns for the .ipa and .dSYM.zip names Change By: Brantone Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22848) Hockeyapp plugin can't publish from remote slaves
Title: Message Title Brantone closed an issue as Fixed Jenkins / JENKINS-22848 Hockeyapp plugin can't publish from remote slaves Change By: Brantone Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-17783) Uploading app doesn't respect App ID
Title: Message Title Brantone closed an issue as Not A Defect Jenkins / JENKINS-17783 Uploading app doesn't respect App ID Change By: Brantone Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-17807) HockeyAppRecorder.getProjectActions throws NullPointerException
Title: Message Title Brantone closed an issue as Fixed Jenkins / JENKINS-17807 HockeyAppRecorder.getProjectActions throws NullPointerException Change By: Brantone Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32760) Unable to get hockeyApp plugin to work
Title: Message Title Brantone closed an issue as Postponed Closing per request Jenkins / JENKINS-32760 Unable to get hockeyApp plugin to work Change By: Brantone Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26059) Expand variables before using conditional
Title: Message Title Brantone closed an issue as Fixed IN 1.2.1 Jenkins / JENKINS-26059 Expand variables before using conditional Change By: Brantone Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22915) In HockeyApp plugin it seems like the "Clean up old versions at HockeyApp" is no longer working
Title: Message Title Brantone assigned an issue to Brantone Jenkins / JENKINS-22915 In HockeyApp plugin it seems like the "Clean up old versions at HockeyApp" is no longer working Change By: Brantone Assignee: Brantone Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22915) In HockeyApp plugin it seems like the "Clean up old versions at HockeyApp" is no longer working
Title: Message Title Brantone closed an issue as Fixed Fixed in 1.2.1 Jenkins / JENKINS-22915 In HockeyApp plugin it seems like the "Clean up old versions at HockeyApp" is no longer working Change By: Brantone Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-23549) HockeyApp Plugin : ArrayIndexOutOfBoundsException
Title: Message Title Brantone closed an issue as Fixed Jenkins / JENKINS-23549 HockeyApp Plugin : ArrayIndexOutOfBoundsException Change By: Brantone Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31171) Hockeyapp Plugin: Support restricting downloads per team
Title: Message Title Brantone commented on JENKINS-31171 Re: Hockeyapp Plugin: Support restricting downloads per team Yup. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31171) Hockeyapp Plugin: Support restricting downloads per team
Title: Message Title Brantone closed an issue as Fixed In 1.2.1 Jenkins / JENKINS-31171 Hockeyapp Plugin: Support restricting downloads per team Change By: Brantone Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36386) Ability to upload xcarchive with HockeyAppPlugin
Title: Message Title Brantone commented on JENKINS-36386 Re: Ability to upload xcarchive with HockeyAppPlugin If I read the KB correctly, this is not supported by HockeyApp. Per https://support.hockeyapp.net/kb/client-integration-ios-mac-os-x-tvos/how-to-upload-to-hockeyapp-from-mac-os-x :: HockeyApp for Mac creates and uploads both the .ipa and the .dSYM file. So the HockeyApp app itself opens the archive and uploads both separately. Even the dashboard page says: Upload .ipa, .apk, and .zip files by dragging them directly on this page. So if I understand the request, it's asking for HockeyApp to be able to take an Xcarchive, open it up and upload both? I think that's beyond the scope of the plugin, but I will entertain reviewing a pull request for such a feature. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
