[JIRA] (JENKINS-33458) Make Sidebar-Link Plugin Compatible With Pipeline
Title: Message Title Max Wahler commented on JENKINS-33458 Re: Make Sidebar-Link Plugin Compatible With Pipeline Are there any updates to this issue? I'd love to see sidebar links back in Jenkins! Our use case is that a build generates data that is sent to Metabase which generates charts to query and visualize the test results. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39773) Check if script needs approval before executing it
Title: Message Title Max Wahler updated an issue Jenkins / JENKINS-39773 Check if script needs approval before executing it Change By: Max Wahler It often happens that I modify a pipeline script, it runs for several minutes in Jenkins and then fails because I added a method call that needs approval. Then I approve that method, run it again and have to hope that there's not another method call I have to approve.So IMHO it'd be great if Jenkins did some kind of "dry run" on a script to check if there's any method signature that still needs approval and immediately fails before the script was actually executed.This may also have severe consequences, e.g. if a component was deployed and the script fails afterwards and it's impossible to roll back the deployment. Also, it's not possible to add script approvals manually using the web interface so I actually have to wait for the script to fail. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are s
[JIRA] (JENKINS-39773) Check if script needs approval before executing it
Title: Message Title Max Wahler created an issue Jenkins / JENKINS-39773 Check if script needs approval before executing it Issue Type: Improvement Assignee: Unassigned Components: pipeline Created: 2016/Nov/16 10:24 AM Priority: Major Reporter: Max Wahler It often happens that I modify a pipeline script, it runs for several minutes in Jenkins and then fails because I added a method call that needs approval. Then I approve that method, run it again and have to hope that there's not another method call I have to approve. So IMHO it'd be great if Jenkins did some kind of "dry run" on a script to check if there's any method signature that still needs approval and immediately fails before the script was actually executed. This may also have severe consequences, e.g. if a component was deployed and the script fails afterwards and it's impossible to roll back the deployment. Add Comment
[JIRA] (JENKINS-36089) Pipeline support for Promoted Builds Plugin
Title: Message Title Max Wahler commented on JENKINS-36089 Re: Pipeline support for Promoted Builds Plugin I just wanted to explain my approach for promoting pipeline builds, maybe it helps others. I have several components and each has a separate build job. All jobs are orchestrated by a build chain job which triggers the other jobs, runs integration tests, etc. After the build chain completed successfully, I use GroovyPostbuildAction.createBadge() to add a badge to the builds that were used during the integration tests. Then I created a promotion job, in which I can select the component and the build number to promote. It then checks if that specific build contains the badge that was previously added (i.e. all tests were successful) and does some action (deploy on production server, upload artifacts, ...). In the promotion job, I also included mechanisms to implement multi-level promotion by using different badges, so that, for example, a release first has to be deployed on the testing servers before it may be deployed to production systems. 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-38005) Using archiveArtifacts with a non-matching pattern silently fails the build
Title: Message Title Max Wahler commented on JENKINS-38005 Re: Using archiveArtifacts with a non-matching pattern silently fails the build Jesse Glick: What would it look like with the modifications you proposed when there's nothing to archive? 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-27421) Unserializable iterator & entry classes from Java Collections
Title: Message Title Max Wahler commented on JENKINS-27421 Re: Unserializable iterator & entry classes from Java Collections Oh dear, all these complications just for the pipelines to be resumable? Is there any other reason for this? Jesse Glick: I really appreciate your work, but me (and I guess 99% of all users) would be fine with a pipeline that's not resumable but that supports all that groovy Groovy stuff without any headaches. It's annoying if you have a huge pipeline that takes dozens of minutes to build just to end up in a NotSerializableException. What about introducing a switch where the user can decide if a pipeline is resumable or not? 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-38005) Using archiveArtifacts with a non-matching pattern silently fails the build
Title: Message Title Max Wahler commented on JENKINS-38005 Re: Using archiveArtifacts with a non-matching pattern silently fails the build Is there any progress on this issue? It would be really really great if there was a way to tell if archiveArtifacts worked or not! I have a job that builds a lot of stuff and has ~750 steps. It's totally impossible to find out where the pipeline failed in case archiveArtifacts failed, because every step is green and there's no output at all that points me to the correct place. My approach is now more a Poor Man's Debugger than a solution: I put masses of printlns in it which give me the current build result. But this doesn't necessarily mean that the error happened at that specific place if you build stuff in parallel. IMHO, archiveArtifacts should at least print out the amount of files it included. Also a return value containing the files or the number of files would be great. But instead of failing silently, I'd prefer an Exception. 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-27299) Refactor Disable Build feature out of AbstractProject for Workflow Compatibility
Title: Message Title Max Wahler commented on JENKINS-27299 Re: Refactor Disable Build feature out of AbstractProject for Workflow Compatibility +1 for this feature! There are so many scenarios that require a job to be disabled that I also think that this is a core 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.
[JIRA] (JENKINS-37327) Allow stashing/unstashing empty sets
Title: Message Title Max Wahler commented on JENKINS-37327 Re: Allow stashing/unstashing empty sets Moreover, stash doesn't include empty directories that might be used after an unstash. 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-38157) multiple new errors on long time running pipelines after latest update
Title: Message Title
Max Wahler commented on JENKINS-38157
Re: multiple new errors on long time running pipelines after latest update
I'm sorry, but IMHO it's ridiculous to say that a NotSerializableException is always a script bug! As part of a script, I create a new job by copying a template and then change some build settings. This is done via
node {
println "create new job"
def job = Hudson.instance.copy(Jenkins.instance.getItem("JobTemplate"), "NewJob")
println "change settings"
changeJobSettings(job, "VERSION", "LATEST")
}
The job was copied but it fails at Hudson.instance.copy with
java.io.NotSerializableException: hudson.model.FreeStyleProject
at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:860)
at org.jboss.marshalling.river.BlockMarshaller.doWriteObject(BlockMarshaller.java:65)
at org.jboss.marshalling.river.BlockMarshaller.writeObject(BlockMarshaller.java:56)
at org.jboss.marshalling.MarshallerObjectOutputStream.writeObjectOverride(MarshallerObjectOutputStream.java:50)
at org.jboss.marshalling.river.RiverObjectOutputStream.writeObjectOverride(RiverObjectOutputStream.java:179)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:344)
at java.util.HashMap.internalWriteEntries(HashMap.java:1785)
at java.util.HashMap.writeObject(HashMap.java:1362)
at sun.reflect.GeneratedMethodAccessor93.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.marshalling.reflect.SerializableClass.callWriteObject(SerializableClass.java:271)
at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:976)
at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:854)
at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1032)
at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:988)
at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:854)
at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1032)
at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:988)
at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:967)
at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:854)
at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1032)
at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:988)
at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:967)
at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:854)
at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1032)
at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:988)
at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:967)
at org.jboss.marshalling.river.RiverMarshaller.do
[JIRA] (JENKINS-27421) Unserializable iterator & entry classes from Java Collections
Title: Message Title
Max Wahler commented on JENKINS-27421
Re: Unserializable iterator & entry classes from Java Collections
I just wanted to say that I started to get confronted with this bug only since my latest Jenkins update today. Before that, a for (String a : items) {} worked perfectly, now I get a java.io.NotSerializableException: java.util.AbstractList$Itr
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-38005) Using archiveArtifacts with a non-matching pattern silently fails the build
Title: Message Title Max Wahler commented on JENKINS-38005 Re: Using archiveArtifacts with a non-matching pattern silently fails the build I raised the priority to 'Critical' because this makes very difficult to see where a large build actually failed. Also, I saw a similar behavior: archiveArtifacts 'target/test.data' fails only if the directory 'target' does not exist. If it exists but not the file 'test.data', then the build fails but the build step was successful. 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-38005) Using archiveArtifacts with a non-matching pattern silently fails the build
Title: Message Title Max Wahler updated an issue Jenkins / JENKINS-38005 Using archiveArtifacts with a non-matching pattern silently fails the build Change By: Max Wahler Priority: Minor Critical 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-38170) Manual approval is stored, even if requirements are not matched
Title: Message Title Max Wahler created an issue Jenkins / JENKINS-38170 Manual approval is stored, even if requirements are not matched Issue Type: Bug Assignee: Oleg Nenashev Components: promoted-builds-plugin Created: 2016/Sep/13 3:00 PM Environment: Jenkins 2.21 on Linux x86-64 Promoted Builds Plugin 2.27 Priority: Critical Reporter: Max Wahler I want to establish a QA pipe like described in the documentation of the plugin. Therefor, I have the following promotion steps: DeployStaging only when manually approved TestedOnStaging only when manually approved when upstream promotions promoted: DeployStaging DeployProduction only when manually approved when upstream promotions promoted: TestedOnStaging So my intention is that first some has to trigger the deployment on the staging server, then it has to be tested and only if that was approved, it can be deployed to the production server. Now when no step was every promoted and I trigger DeployProduction, it correctly tells me "Unmet qualification: TestedOnStaging". Then I trigger TestedOnStaging and it correctly tells me that DeployStaging qualification was not met. But if I n
[JIRA] (JENKINS-38131) Can't read file with Groovy API
Title: Message Title Max Wahler created an issue Jenkins / JENKINS-38131 Can't read file with Groovy API Issue Type: Bug Assignee: Craig Rodrigues Components: build-flow-plugin Created: 2016/Sep/12 10:48 AM Environment: OSX 10.11.6 Priority: Critical Reporter: Max Wahler I have a file in my workspace that was generated by a Maven plugin. When I try to read it with new File(filename).text a FileNotFoundException was thrown although the file exists. The pipeline doesn't run in a sandbox and there's no method to approve at the In-process Script Approval view. But I'm able to read that file using the pipeline's readFile method. I tried both a relative as well as an absolute path to the file. Is there anything I'm missing or is this a bug? Add Comment
[JIRA] (JENKINS-38059) Script editor should remember size
Title: Message Title Max Wahler created an issue Jenkins / JENKINS-38059 Script editor should remember size Issue Type: Improvement Assignee: Craig Rodrigues Components: build-flow-plugin Created: 2016/Sep/08 12:58 PM Priority: Minor Reporter: Max Wahler Everytime I configure a pipeline job, the script editor window gets its initial size even if I resized it on the last time. That's annoying if you want to edit a script that's longer than a few lines. In comparison, the "Execute shell" step remembers the editor's size. Add Comment
[JIRA] (JENKINS-38027) withMaven disabled AnsiColorBuildWrapper
Title: Message Title
Max Wahler created an issue
Jenkins / JENKINS-38027
withMaven disabled AnsiColorBuildWrapper
Issue Type:
Bug
Assignee:
Alvaro Lobato
Components:
pipeline-maven-plugin
Created:
2016/Sep/07 1:14 PM
Priority:
Minor
Reporter:
Max Wahler
I built a pipeline job which uses both the AnsiColorBuildWrapper and the Pipeline Maven plugin. When I call: withMaven(jdk: 'Java8 Auto Install', maven: 'Maven 3.2.2 Auto Install', mavenLocalRepo: '', mavenOpts: '', mavenSettingsFilePath: '') { wrap([$class: 'AnsiColorBuildWrapper']) { sh "mvn clean install" } } I correctly get a colored output. But if I switch the "withMaven" and the "wrap" blocks, I just see the control characters. I consider this a (minor) bug.
Add Comment
[JIRA] (JENKINS-37283) After provisioning profile was updated, the job setting was reset
Title: Message Title Max Wahler created an issue Jenkins / JENKINS-37283 After provisioning profile was updated, the job setting was reset Issue Type: Bug Assignee: Unassigned Components: kpp-management-plugin Created: 2016/Aug/09 4:37 PM Priority: Major Reporter: Max Wahler When I renew a provisioning profile and upload it to Jenkins with the same file name, it gets replaced in the management view but unfortunately not in the different jobs. It would be great if that was done automatically! Add Comment
[JIRA] [confluence-publisher-plugin] (JENKINS-32412) Build should fail if upload failed
Title: Message Title Max Wahler updated an issue Jenkins / JENKINS-32412 Build should fail if upload failed Change By: Max Wahler Priority: Minor Critical Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [confluence-publisher-plugin] (JENKINS-32412) Build should fail if upload failed
Title: Message Title Max Wahler created an issue Jenkins / JENKINS-32412 Build should fail if upload failed Issue Type: Bug Assignee: Joe Hansche Components: confluence-publisher-plugin Created: 12/Jan/16 1:00 PM Priority: Minor Reporter: Max Wahler The confluence user configured had insufficient permissions to attach a file to a page, so a com.atlassian.confluence.rpc.NotPermittedException: You do not have the permissions to perform this action was thrown. Nevertheless, the build status was SUCCESS. In my opinion, there should be at least a flag if the build should fail if the upload failed. Add Comment
[JIRA] [android-emulator-plugin] (JENKINS-22334) plugin thinks emulator always crashes using sdk 22.6.1
Title: Message Title Max Wahler commented on JENKINS-22334 Re: plugin thinks emulator always crashes using sdk 22.6.1 I'm experiencing the issue now after updating from 2.12 to 2.13.1. I use the latest Android SDK & tools. After the emulator was started, I see two devices albeit only one emulator instance is running: Mac-mini-Yosemite:~ blueid$ /opt/android-sdk/platform-tools/adb -P 6813 devices List of devices attached emulator-6811 device localhost:6812 device Is this some kind of regression? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobconfighistory-plugin] (JENKINS-6659) Record a change message along with the job change history
Max Wahler commented on JENKINS-6659 Record a change message along with the job change history Great idea! Sometimes, there are lots of changes to a job and if you want to revert something, you have to go through many diffs. I'd also love a setting to make the change reason mandatory for specific jobs! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-25790) New adb connect command always fails to connect emulator on OS X
Max Wahler commented on JENKINS-25790 New adb connect command always fails to connect emulator on OS X I can confirm this issue! Mostly the emulator says something like "socket already connected". This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [security] (JENKINS-25333) Jenkins 1.586 not starting up using Java8
Max Wahler created JENKINS-25333 Jenkins 1.586 not starting up using Java8 Issue Type: Bug Assignee: Unassigned Components: security Created: 28/Oct/14 9:44 AM Description: Using Java8, Jenkins doesn't start with the following message: SCHWERWIEGEND: Container startup failed java.io.IOException: Failed to start a listener: winstone.HttpsConnectorFactory at winstone.Launcher.spawnListener(Launcher.java:209) at winstone.Launcher.(Launcher.java:149) at winstone.Launcher.main(Launcher.java:354) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at Main._main(Main.java:293) at Main.main(Main.java:98) Caused by: java.lang.NoClassDefFoundError: sun/security/x509/CertAndKeyGen at winstone.HttpsConnectorFactory.start(HttpsConnectorFactory.java:101) at winstone.Launcher.spawnListener(Launcher.java:207) ... 8 more Caused by: java.lang.ClassNotFoundException: sun.security.x509.CertAndKeyGen at java.net.URLClassLoader$1.run(URLClassLoader.java:372) at java.net.URLClassLoader$1.run(URLClassLoader.java:361) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:360) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ... 10 more After switching back to Oracle Java 7, it works without problems. Environment: Debian 7 Wheezy x86-64, Oracle Java 8, Jenkins 1.586 Project: Jenkins Labels: jenkins exception Priority: Critical Reporter: Max Wahler This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobconfighistory] (JENKINS-23527) Job configuration history is missing (not recorded) for some jobs
Max Wahler commented on JENKINS-23527 Job configuration history is missing (not recorded) for some jobs I have the same problem. As far as I can see this only appears to happen on maven2-modulesets. Maybe it's really related to core updates because there are other issues with this kind of jobs too. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [thinBackup] (JENKINS-18093) thinBackup stops if there's no unstable build
Max Wahler created JENKINS-18093 thinBackup stops if there's no unstable build Issue Type: Bug Affects Versions: current Assignee: Thomas Fürer Components: thinBackup Created: 27/May/13 7:33 AM Description: Usually, every job has a symlink from builds/lastUnstableBuild und builds/-1 if there's no unstable build yet but that "-1" directory does not exist usually. thinBackup then logs that this directory does not exist and stops the backup completely. Project: Jenkins Priority: Major Reporter: Max Wahler This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-17680) Upgrade to new Copy Artifacts version erases all job names to copy from
Max Wahler commented on JENKINS-17680 Upgrade to new Copy Artifacts version erases all job names to copy from I've also seen this issue. In 1.26, the tag name changed from projectName to project. I edited all our config.xml files manually and it does the trick. Bad news is, that saving the configuration in Jenkins throws an exception. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
