[JIRA] (JENKINS-53976) ALM needs to change code structure
Title: Message Title Daniel Gront created an issue Jenkins / JENKINS-53976 ALM needs to change code structure Issue Type: Task Assignee: Roy Lu Components: hp-application-automation-tools-plugin Created: 2018-10-10 06:26 Labels: ALM 5.6 Priority: Major Reporter: Daniel Gront All files the solely under the responsibility of ALM should be moved under their own folder named "alm". An inner structure could me separated if wanted to Lab Management/ SSE / Test Result Uploader. Add Comment
[JIRA] (JENKINS-53975) SRF needs to change code structure
Title: Message Title Daniel Gront created an issue Jenkins / JENKINS-53975 SRF needs to change code structure Issue Type: Task Assignee: noam doron Components: hp-application-automation-tools-plugin Created: 2018-10-10 06:21 Labels: SRF 5.6 Priority: Major Reporter: Daniel Gront All files the solely under the responsibility of SRF should be moved under their own folder named "srf". Add Comment
[JIRA] (JENKINS-53974) SV needs to change code strucutre
Title: Message Title Daniel Gront created an issue Jenkins / JENKINS-53974 SV needs to change code strucutre Issue Type: Task Assignee: michael jing Components: hp-application-automation-tools-plugin Created: 2018-10-10 06:18 Labels: 5.6 ServiceVirtualization Priority: Major Reporter: Daniel Gront All files the solely under the responsibility of SV should be moved under their own folder named "sv". Add Comment
[JIRA] (JENKINS-53973) UFT needs to change code structure
Title: Message Title Daniel Gront created an issue Jenkins / JENKINS-53973 UFT needs to change code structure Issue Type: Task Assignee: Anda Sorina Laakso Components: hp-application-automation-tools-plugin Created: 2018-10-10 06:13 Labels: UFT 5.6 Priority: Major Reporter: Daniel Gront Tamas Florin All files the solely under the responsibility of UFT should be moved under their own folder named "uft". Add Comment
[JIRA] (JENKINS-53972) Octane needs to change code structure
Title: Message Title Daniel Gront created an issue Jenkins / JENKINS-53972 Octane needs to change code structure Issue Type: Task Assignee: Michael Seldin Components: hp-application-automation-tools-plugin Created: 2018-10-10 06:10 Labels: 5.6 octane Priority: Major Reporter: Daniel Gront All files the solely under the responsibility of Octane should be moved under their own folder. Add Comment
[JIRA] (JENKINS-53971) MC needs to change code structure
Title: Message Title Daniel Gront created an issue Jenkins / JENKINS-53971 MC needs to change code structure Issue Type: Task Assignee: Jane Zhang Components: hp-application-automation-tools-plugin Created: 2018-10-10 06:09 Labels: 5.6 MobileCenter Priority: Major Reporter: Daniel Gront All files the solely under the responsibility of MC should be moved under their own folder named "mc". Add Comment
[JIRA] (JENKINS-53970) LR needs to change code structure
Title: Message Title Daniel Gront created an issue Jenkins / JENKINS-53970 LR needs to change code structure Issue Type: Task Assignee: Rolando-Mihai Vlad Components: hp-application-automation-tools-plugin Created: 2018-10-10 06:07 Labels: LR 5.6 Priority: Major Reporter: Daniel Gront All files the solely under the responsibility of LR should be moved under their own folder named "lr". Add Comment
[JIRA] (JENKINS-53968) The hirearchy of the packages needs to change
Title: Message Title Daniel Gront updated an issue Jenkins / JENKINS-53968 The hirearchy of the packages needs to change Change By: Daniel Gront Labels: 5.6 Joint 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-53968) The hirearchy of the packages needs to change
Title: Message Title Daniel Gront updated an issue Jenkins / JENKINS-53968 The hirearchy of the packages needs to change Change By: Daniel Gront The current package/files structure is not separated per product, hence the responsibility of files cannot be decided.Each product should move the classes that are solely under his and not shared between multiple products under his product name for example "pc" folder.For example, RunFromFileBuilder.class is used by UFT, LR, MC and should stay in his current location until moved by me.The inner structure of the files inside your product name is for your own choosing.For reference, you can view SRF/Octane which folders. *Do not forget about moving the resources as well (jelly files), their location is critical.* 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-51545) Bug in Build Monitor View Plugin
Title: Message Title Tapio Reijonen commented on JENKINS-51545 Re: Bug in Build Monitor View Plugin We find out this issue also. When unset Build Monitor - Widget Settings, Display committers option, the view works ok. Well, no committers displayed. We noticed that only some views was broken after upgrade this pluging, e.g. is the problem some how related authenticate committers? 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-53969) PC needs to change code structure
Title: Message Title Daniel Gront created an issue Jenkins / JENKINS-53969 PC needs to change code structure Issue Type: Task Assignee: Daniel Danan Components: hp-application-automation-tools-plugin Created: 2018-10-10 06:04 Labels: PerformanceCenter Priority: Major Reporter: Daniel Gront All files under PC responsibility should be moved to a folder called "pc". Add Comment
[JIRA] (JENKINS-53968) The hirearchy of the packages needs to change
Title: Message Title Daniel Gront created an issue Jenkins / JENKINS-53968 The hirearchy of the packages needs to change Issue Type: Epic Assignee: Daniel Gront Components: hp-application-automation-tools-plugin Created: 2018-10-10 06:02 Labels: 5.6 Priority: Major Reporter: Daniel Gront The current package/files structure is not separated per product, hence the responsibility of files cannot be decided. Each product should move the classes that are solely under his and not shared between multiple products under his product name for example "pc" folder. For example, RunFromFileBuilder.class is used by UFT, LR, MC and should stay in his current location until moved by me. The inner structure of the files inside your product name is for your own choosing. For reference, you can view SRF/Octane which folders. Add Comment
[JIRA] (JENKINS-53576) Configuration-as-Code compatibility
Title: Message Title Jon Brohauge commented on JENKINS-53576 Re: Configuration-as-Code compatibility I can see that the PR in GitHub has been merged. Is there a set release date for the updated plugin? 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-53761) JIRA Plugin in multibranch pipeline showing all previous build tickets also in current build changes
Title: Message Title Rajguru Parambath assigned an issue to Martin Sander Jenkins / JENKINS-53761 JIRA Plugin in multibranch pipeline showing all previous build tickets also in current build changes Change By: Rajguru Parambath Assignee: Martin Sander 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-53967) Looking for option to find git push user
Title: Message Title Eldo Joseph created an issue Jenkins / JENKINS-53967 Looking for option to find git push user Issue Type: Improvement Assignee: Mark Waite Components: git-plugin Created: 2018-10-10 02:17 Environment: PROD Labels: git-plugin Priority: Minor Reporter: Eldo Joseph When I trigger builds using git push, I could see build home message like "Started by GitHub push by x". I want to pull this information to send notification. Could someone guide me to find the right process? I tried with currentBuild.rawBuild.getCauses() but not helping. Add Comment
[JIRA] (JENKINS-53966) Import Developer Profile in to keychain.
Title: Message Title Kazuhide Takahashi created an issue Jenkins / JENKINS-53966 Import Developer Profile in to keychain. Issue Type: Task Assignee: Unassigned Components: xcode-plugin Created: 2018-10-10 01:57 Priority: Minor Reporter: Kazuhide Takahashi The Xcode Plugin has a function to read secret keys and certificates for code signature from the developer profile in the temporary key chain, but limitation of macOS it is not possible to switch the environment of the keychain for each session. If you run multiple jobs on single node, it will cause a problem. Add Comment
[JIRA] (JENKINS-53965) ConsoleLog is missing build output
Title: Message Title Vivek Pandey commented on JENKINS-53965 Re: ConsoleLog is missing build output Hi Brian Moyle what version of workflow-job, workflow-api and workflow-support plugin are you using? cc: Jesse Glick 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-53961) Adding local jar file to hpi
Title: Message Title Oleg Nenashev commented on JENKINS-53961 Re: Adding local jar file to hpi TBH I am against having such kind of dependencies in Jenkins. It causes a number of issues in dependency scan tools. What does block you from just deploying the library to Maven Central. CC Daniel Beck, you might be interested 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-53962) Job DSL Support without Dynamic DSL
Title: Message Title Oleg Nenashev commented on JENKINS-53962 Re: Job DSL Support without Dynamic DSL I will be happy to review pull requests. The plugin is up for adoption in general, so any contributions are welcome. 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-53962) Job DSL Support without Dynamic DSL
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-53962 Job DSL Support without Dynamic DSL Change By: Oleg Nenashev Assignee: Oleg Nenashev 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-53953) Downstream projects are not triggered if dependencies have a non null classifier
Title: Message Title Cyrille Le Clerc commented on JENKINS-53953 Re: Downstream projects are not triggered if dependencies have a non null classifier Thanks Olivier Pinel. I have created the branch https://github.com/jenkinsci/pipeline-maven-plugin/tree/JENKINS-53953 and it unfortunately has some unit test failures: https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fpipeline-maven-plugin/detail/JENKINS-53953/1/pipeline https://github.com/jenkinsci/pipeline-maven-plugin/pull/166 I am checking on my laptop 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-47137) Blue ocean won't create or edit jenkinsfile when using git
Title: Message Title John Behm reopened an issue see my first comment Jenkins / JENKINS-47137 Blue ocean won't create or edit jenkinsfile when using git Change By: John Behm Resolution: Duplicate Status: Closed Reopened 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-47137) Blue ocean won't create or edit jenkinsfile when using git
Title: Message Title John Behm commented on JENKINS-47137 Re: Blue ocean won't create or edit jenkinsfile when using git Have likely the same issue: My setup: Gitea for code hosting, a fork of Gogs So I have an already existing repository that contains a c/c++ project where the default branch is not called master, but zCatch. What I want to do is to create a simple pipeline in blue ocean that only executes some existing build scripts in a folder. What I want Blue ocean/jenkins to do is to simply add a jenkins file to the source's root folder and not to do anything else. What it actually does is to seemingly overwrite the branch or something for me not understandable, because after Blue ocean adds my pipeline, all I am left with is with my zCatch branch with only a jenkinsfile and the rest of the code is gone. The commit history only seems to show one commit that is the one Blue ocean created. 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-34218) Shallow clone broken after JENKINS-24728
Title: Message Title Michal Wesolowski commented on JENKINS-34218 Re: Shallow clone broken after JENKINS-24728 It breaks when using Shallow clone with depth 1 together with wildcard or regex branch specifier: 15:19:14 Seen 47 remote branches 15:19:14 > git show-ref --tags -d # timeout=10 15:19:14 FATAL: Walk failure. 15:19:14 org.eclipse.jgit.errors.MissingObjectException: Missing commit 07fd7f0f9059f329a98f0f255f6c3d22b08f0dba 15:19:14 at org.eclipse.jgit.internal.storage.file.WindowCursor.open(WindowCursor.java:159) 15:19:14 at org.eclipse.jgit.revwalk.RevWalk.getCachedBytes(RevWalk.java:903) 15:19:14 at org.eclipse.jgit.revwalk.RevCommit.parseHeaders(RevCommit.java:155) 15:19:14 at org.eclipse.jgit.revwalk.PendingGenerator.next(PendingGenerator.java:147) 15:19:14 at org.eclipse.jgit.revwalk.StartGenerator.next(StartGenerator.java:184) 15:19:14 at org.eclipse.jgit.revwalk.RevWalk.next(RevWalk.java:435) 15:19:14 at org.eclipse.jgit.revwalk.RevWalk.iterator(RevWalk.java:1322) 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-34218) Shallow clone broken after JENKINS-24728
Title: Message Title Michal Wesolowski updated JENKINS-34218 Jenkins / JENKINS-34218 Shallow clone broken after JENKINS-24728 Change By: Michal Wesolowski Status: Resolved In Review 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-53965) ConsoleLog is missing build output
Title: Message Title Brian Moyle edited a comment on JENKINS-53965 Re: ConsoleLog is missing build output sorry – not sure how to include the code snippet above with without the markup getting in the way and creating the strike-through text. 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-53965) ConsoleLog is missing build output
Title: Message Title Brian Moyle commented on JENKINS-53965 Re: ConsoleLog is missing build output sorry – not sure how to include the code snippet above with the markup getting in the way and creating the strike-through text. 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-53965) ConsoleLog is missing build output
Title: Message Title
Brian Moyle updated an issue
Jenkins / JENKINS-53965
ConsoleLog is missing build output
Change By:
Brian Moyle
I have run into an issue with the Console Output often failing to include build failure messages, due to the output being truncated.In an attempt to discover why our builds were failing, I discovered the transient durable jenkins-log.txt file(s) - they appear to be removed upon completion of the build.(e.g., ... /project@tmp/durable-472431c5/jenkins-log.txt)I also noticed I could tail the file to eventually find failures in our build, and in the process, I realized this file seems to be getting reset/truncated, and the remaining log messages appear to start from the beginning of the file. I'm assuming this may explain the lack of progress in the Console Output, which stops progressing beyond this point, and is often missing important build failure information.I don't know what causes it, but I have tried a "tail -F jenkins-log.txt >> saved_log.txt 2>&1" on the file, and see something similar to: {{ [... snip ...] }} {{ >>> qt5base 5.6.2 Configuring }} {{ /usr/bin/install -m 0644 -D package/qt5/qt5base//qmake.conf /var/lib/jenkins/workspace/top_project/sub_project/ver_4.7.3/output/build/qt5base-5.6.2/mkspecs/devices/linux-buildroot-g++/qmake.conf }} {{ /usr/bin/install -m 0644 -D package/qt5/qt5base//qplatformdefs.h /var/lib/jenkins/workspace/top_project/sub_project/ver_4.7.3/output/build/qt5base-5.6.2/mkspecs/devices/linux-buildroot-g++/qplatformdefs.h }} {{ (cd /var/lib/jenkins/workspace/top_project/sub_project/ver_4.7.3/output/build/qt5base-5.6.2; PATH="/var/lib/jenkins/workspace/top_project/sub_project/ver_4.7.3/output/host/bin:/var/lib/jenkins/workspace/top_project/sub_project/ver_4.7.3/output/host/sbin:/var/lib/jenkins/workspace/top_project/sub_project/ver_4.7.3/output/host/usr/bin:/var/lib/jenkins/workspace/top_project/sub_project/ver_4.7.3/output/host/usr/sbin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/snap/bin" PKG_CONFIG="/var/lib/jenkins/workspace/top_project/sub_project/ver_4.7.3/output/host/usr/bin/pkg-config" PKG_CONFIG_LIBDIR="/var/lib/jenkins/workspace/top_project/sub_project/ver_4.7.3/output/host/usr/arm-buildroot-linux-gnueabihf/sysroot/usr/lib/pkgconfig" PKG_CONFIG_SYSROOT_DIR="/var/lib/jenkins/workspace/top_project/sub_project/ver_4.7.3/output/host/usr/arm-buildroot-linux-gnueabihf/sysroot" MAKEFLAGS=" – V=1 -j29" ./configure -v -prefix /usr -hostprefix /var/lib/jenkins/workspace/top_project/sub_project/ver_4.7.3/output/host/usr -headerdir /usr/include/qt5 -sysroot /var/lib/jenkins/workspace/top_project/sub_project/ver_4.7.3/output/host/usr/arm-buildroot-linux-gnueabihf/sysroot -plugindir /usr/lib/qt/plugins -examplesdir /usr/lib/qt/examples -no-rpath -nomake tests -device buildroot -device-option CROSS_COMPILE="/var/lib/jenkins/workspace/top_project/sub_project/ver_4.7.3/output/host/usr/bin/arm-cortexa9_neon-linux-gnueabihf-" -device-option BR_COMPILER_CFLAGS="-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET
[JIRA] (JENKINS-53965) ConsoleLog is missing build output
Title: Message Title Brian Moyle updated an issue Jenkins / JENKINS-53965 ConsoleLog is missing build output Change By: Brian Moyle I have run into an issue with ConsoleLog the Console Output often failing to include build failure messages, due to the output being truncated.In an attempt to discover why our builds were failing, I discovered the transient durable jenkins-log.txt file(s) - they appear to be removed upon completion of the build.(e.g., ... /project@tmp/durable-472431c5/jenkins-log.txt)I also noticed I could tail the file to eventually find failures in our build, and in the process, I realized this file seems to be getting reset/truncated, and the remaining log messages appear to start from the beginning of the file. I'm assuming this may explain the lack of progress in the ConsoleLog output Console Output , which stops progressing beyond this point, and is often missing important build failure information.I don't know what causes it, but I have tried a "tail -F jenkins-log.txt >> saved_log.txt 2>&1" on the file, and see something similar to:[... snip ...] >>> qt5base 5.6.2 Configuring /usr/bin/install -m 0644 -D package/qt5/qt5base//qmake.conf /var/lib/jenkins/workspace/top_project/sub_project/ver_4.7.3/output/build/qt5base-5.6.2/mkspecs/devices/linux-buildroot-g++/qmake.conf /usr/bin/install -m 0644 -D package/qt5/qt5base//qplatformdefs.h /var/lib/jenkins/workspace/top_project/sub_project/ver_4.7.3/output/build/qt5base-5.6.2/mkspecs/devices/linux-buildroot-g++/qplatformdefs.h (cd /var/lib/jenkins/workspace/top_project/sub_project/ver_4.7.3/output/build/qt5base-5.6.2; PATH="/var/lib/jenkins/workspace/top_project/sub_project/ver_4.7.3/output/host/bin:/var/lib/jenkins/workspace/top_project/sub_project/ver_4.7.3/output/host/sbin:/var/lib/jenkins/workspace/top_project/sub_project/ver_4.7.3/output/host/usr/bin:/var/lib/jenkins/workspace/top_project/sub_project/ver_4.7.3/output/host/usr/sbin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/snap/bin" PKG_CONFIG="/var/lib/jenkins/workspace/top_project/sub_project/ver_4.7.3/output/host/usr/bin/pkg-config" PKG_CONFIG_LIBDIR="/var/lib/jenkins/workspace/top_project/sub_project/ver_4.7.3/output/host/usr/arm-buildroot-linux-gnueabihf/sysroot/usr/lib/pkgconfig" PKG_CONFIG_SYSROOT_DIR="/var/lib/jenkins/workspace/top_project/sub_project/ver_4.7.3/output/host/usr/arm-buildroot-linux-gnueabihf/sysroot" MAKEFLAGS=" – V=1 -j29" ./configure -v -prefix /usr -hostprefix /var/lib/jenkins/workspace/top_project/sub_project/ver_4.7.3/output/host/usr -headerdir /usr/include/qt5 -sysroot /var/lib/jenkins/workspace/top_project/sub_project/ver_4.7.3/output/host/usr/arm-buildroot-linux-gnueabihf/sysroot -plugindir /usr/lib/qt/plugins -examplesdir /usr/lib/qt/examples -no-rpath -nomake tests -device buildroot -device-option CROSS_COMPILE="/var/lib/jenkins/workspace/top_project/sub_project/ver_4.7.3/output/host/usr/bin/arm-cortexa9_neon-linux-gnueabihf-" -device-option BR_COMPILER_CFLAGS="-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_
[JIRA] (JENKINS-53965) ConsoleLog is missing build output
Title: Message Title Brian Moyle created an issue Jenkins / JENKINS-53965 ConsoleLog is missing build output Issue Type: Bug Assignee: Unassigned Components: durable-task-plugin Created: 2018-10-09 19:36 Environment: Linux x86_64 (Ubuntu 16.04), Jenkins 2.121.1, Chrome (on MacOS) Priority: Minor Reporter: Brian Moyle I have run into an issue with ConsoleLog often failing to include build failure messages, due to the output being truncated. In an attempt to discover why our builds were failing, I discovered the transient durable jenkins-log.txt file(s) - they appear to be removed upon completion of the build. (e.g., ... /project@tmp/durable-472431c5/jenkins-log.txt) I also noticed I could tail the file to eventually find failures in our build, and in the process, I realized this file seems to be getting reset/truncated, and the remaining log messages appear to start from the beginning of the file. I'm assuming this may explain the lack of progress in the ConsoleLog output, which stops progressing beyond this point, and is often missing important build failure information. I don't know what causes it, but I have tried a "tail -F jenkins-log.txt >> saved_log.txt 2>&1" on the file, and see something similar to: [... snip ...] >>> qt5base 5.6.2 Configuring /usr/bin/install -m 0644 -D package/qt5/qt5base//qmake.conf /var/lib/jenkins/workspace/top_project/sub_project/ver_4.7.3/output/build/qt5base-5.6.2/mkspecs/devices/linux-buildroot-g++/qmake.conf /usr/bin/install -m 0644 -D package/qt5/qt5base//qplatformdefs.h /var/lib/jenkins/workspace/top_project/sub_project/ver_4.7.3/output/build/qt5base-5.6.2/mkspecs/devices/linux-buildroot-g++/qplatformdefs.h (cd /var/lib/jenkins/workspace/top_project/sub_project/ver_4.7.3/o
[JIRA] (JENKINS-53476) Automatic update prompts within Jenkins should be disabled
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-53476 Automatic update prompts within Jenkins should be disabled Change By: Baptiste Mathus Labels: newbie-friendly 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-53476) Automatic update prompts within Jenkins should be disabled
Title: Message Title Baptiste Mathus assigned an issue to Unassigned Jenkins / JENKINS-53476 Automatic update prompts within Jenkins should be disabled Change By: Baptiste Mathus Assignee: Baptiste Mathus 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-53476) Automatic update prompts within Jenkins should be disabled
Title: Message Title Baptiste Mathus commented on JENKINS-53476 Re: Automatic update prompts within Jenkins should be disabled R. Tyler Croy I think this one could be made clearer. I think I see what you mean, but ideally evergreen tasks should be doable not only by us knowing well both Jenkins and Evergreen context. IIUC, this is about the so-called Administrative Monitor displayed under /configure when a new version of Jenkins is available . If so, there's already some food for thought in https://groups.google.com/forum/#!msg/jenkinsci-users/TSY2MhkTNJ4/8Qc9yMFGBgAJ More specfically: https://groups.google.com/d/msg/jenkinsci-users/TSY2MhkTNJ4/mLgot1oKAgAJ Go to Manage Jenkins> Configure System> Administrative monitors configuration and uncheck Jenkins Update Notification box and save the settings and refresh jenkins page. Now you should not see the jenkins new version update notification. I think the right way inside Evergreen to achieve this is to find a way to "check" this checkbox (i.e. disable this administrative monitor) using JCasC. Seems like the code inside Jenkins is https://github.com/jenkinsci/jenkins/blob/b057abc7b84295969b894d06011e250842c6d09c/core/src/main/java/hudson/model/UpdateCenter.java#L981-L999 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-37588) Multibranch pipeline does not allow quiet time or throttle
Title: Message Title John Muczynski commented on JENKINS-37588 Re: Multibranch pipeline does not allow quiet time or throttle Ooph, my bad. I didn't make sure to update Declarative to version 1.3.2 It looks like it is accepting the quietPeriod now, after updating blue ocean. 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-53503) More test coverage for Snapshotter.git()
Title: Message Title Baptiste Mathus assigned an issue to Unassigned Jenkins / JENKINS-53503 More test coverage for Snapshotter.git() Change By: Baptiste Mathus Assignee: Baptiste Mathus 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-51877) Write JEP about auto-configuration for a given environment (Docker, Azure, AWS...)
Title: Message Title Baptiste Mathus assigned an issue to Unassigned Jenkins / JENKINS-51877 Write JEP about auto-configuration for a given environment (Docker, Azure, AWS...) Change By: Baptiste Mathus Assignee: Baptiste Mathus 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-53503) More test coverage for Snapshotter.git()
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-53503 More test coverage for Snapshotter.git() Change By: Baptiste Mathus Labels: evergreen newbie-friendly technical-debt 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-51877) Write JEP about auto-configuration for a given environment (Docker, Azure, AWS...)
Title: Message Title Baptiste Mathus closed an issue as Won't Fix I do not see the need anymore/currently for this one. We will reopen if somebody disagrees (with the right arguments ). Jenkins / JENKINS-51877 Write JEP about auto-configuration for a given environment (Docker, Azure, AWS...) Change By: Baptiste Mathus Status: Open Closed Resolution: Won't Fix 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-53284) Changing default layout for workspace and builds should not be a warning for first time startup
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-53284 Changing default layout for workspace and builds should not be a warning for first time startup Change By: Baptiste Mathus Labels: evergreen evergreen-triggered newbie-friendly 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-53284) Changing default layout for workspace and builds should not be a warning for first time startup
Title: Message Title Baptiste Mathus assigned an issue to Unassigned Jenkins / JENKINS-53284 Changing default layout for workspace and builds should not be a warning for first time startup Change By: Baptiste Mathus Assignee: Baptiste Mathus 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-52342) Refine S3 security policy to only allow access to the created bucket
Title: Message Title Baptiste Mathus assigned an issue to Unassigned Jenkins / JENKINS-52342 Refine S3 security policy to only allow access to the created bucket Change By: Baptiste Mathus Assignee: Baptiste Mathus 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-52570) SSHLocation parameter in CloudFormation template is ignored
Title: Message Title Baptiste Mathus assigned an issue to Unassigned Jenkins / JENKINS-52570 SSHLocation parameter in CloudFormation template is ignored Change By: Baptiste Mathus Assignee: Baptiste Mathus 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-50669) Expose WebAppMain#DEFAULT_RING_BUFFER_SIZE actual value
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-50669 Expose WebAppMain#DEFAULT_RING_BUFFER_SIZE actual value Change By: Baptiste Mathus Sprint: Evergreen - Milestone 2 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-50669) Expose WebAppMain#DEFAULT_RING_BUFFER_SIZE actual value
Title: Message Title Baptiste Mathus assigned an issue to Unassigned Jenkins / JENKINS-50669 Expose WebAppMain#DEFAULT_RING_BUFFER_SIZE actual value Change By: Baptiste Mathus Assignee: Baptiste Mathus 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-49860) Auto-configure AWS agent provisioning when the instance has IAM credentials
Title: Message Title Baptiste Mathus closed an issue as Fixed Jenkins / JENKINS-49860 Auto-configure AWS agent provisioning when the instance has IAM credentials Change By: Baptiste Mathus Status: Open Closed Resolution: Fixed 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-49860) Auto-configure AWS agent provisioning when the instance has IAM credentials
Title: Message Title Baptiste Mathus commented on JENKINS-49860 Re: Auto-configure AWS agent provisioning when the instance has IAM credentials This one is already done. AWS flavor overall is broken currently, but will get back to it as soon as possible. But this has been done already as can be seen on the demo video available at https://jenkins.io/blog/2018/07/10/jenkins-essentials-on-aws/ 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-50940) Introduce a way to have build data only during Evergreen testing
Title: Message Title Baptiste Mathus assigned an issue to Unassigned Jenkins / JENKINS-50940 Introduce a way to have build data only during Evergreen testing Change By: Baptiste Mathus Assignee: Baptiste Mathus 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-53551) Map log levels sent to Sentry
Title: Message Title Baptiste Mathus assigned an issue to Unassigned Jenkins / JENKINS-53551 Map log levels sent to Sentry Change By: Baptiste Mathus Assignee: R. Tyler Croy 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-50429) Shell command are really slower than before
Title: Message Title Pascal Laporte commented on JENKINS-50429 Re: Shell command are really slower than before Carlos Sanchez Do you have any progress on this issue. We would like to upgrade our Kubernetes plugin. But, we won't be able until the performance issue with the «container» step is fix. Thanks for your help 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-53551) Map log levels sent to Sentry
Title: Message Title Baptiste Mathus assigned an issue to R. Tyler Croy Jenkins / JENKINS-53551 Map log levels sent to Sentry Change By: Baptiste Mathus Assignee: Baptiste Mathus R. Tyler Croy 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-53964) Drop uuid_checksum_uniq unique key constraint
Title: Message Title Baptiste Mathus updated JENKINS-53964 Jenkins / JENKINS-53964 Drop uuid_checksum_uniq unique key constraint Change By: Baptiste Mathus Status: In Progress Review 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-37588) Multibranch pipeline does not allow quiet time or throttle
Title: Message Title
John Muczynski commented on JENKINS-37588
Re: Multibranch pipeline does not allow quiet time or throttle
Ah, okay, as Jesse commented on the other issue: "Nothing to do with Declarative vs. Scripted, only multibranch vs. standalone."
options {
buildDiscarder(logRotator(numToKeepStr: '90', artifactNumToKeepStr: '5'))
retry(1)
skipDefaultCheckout()
disableConcurrentBuilds()
quietPeriod(600)
}
org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: WorkflowScript: 350: Invalid option type "quietPeriod". Valid option types: [buildDiscarder, catchError, disableConcurrentBuilds, overrideIndexTriggers, retry, script, skipDefaultCheckout, skipStagesAfterUnstable, timeout, timestamps, waitUntil, withContext, withCredentials, withEnv, ws] @ line 350, column 9. quietPeriod(600) ^ General error during semantic analysis: There's no @DataBoundConstructor on any constructor of class jenkins.model.GlobalQuietPeriodConfiguration org.kohsuke.stapler.NoStaplerConstructorException: There's no @DataBoundConstructor on any constructor of class jenkins.model.GlobalQuietPeriodConfiguration at org.kohsuke.stapler.ClassDescriptor.loadConstructorParamNames(ClassDescriptor.java:265) at org.jenkinsci.plugins.structs.describable.DescribableModel.(DescribableModel.java:122)
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-53964) Drop uuid_checksum_uniq unique key constraint
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-53964 Drop uuid_checksum_uniq unique key constraint Issue Type: Bug Assignee: R. Tyler Croy Components: evergreen Created: 2018-10-09 18:47 Labels: evergreen Priority: Critical Reporter: Baptiste Mathus Problem statement The versions table has a unique key constraint on the checksum and uuid fields. This is a problem because when the reportVersions call is made after a rollback, the insertion is rejected since it would violate that constraint. But in case of a rollback, this is absolutely normal and expected that we are going to get back to a previous known state, so the backend should not reject it. Currently, this is rejected like the following: backend_1 | error: Error during call: BadRequest: Validation error instance_1 | error: Failed to report versions message=Validation error, type=FeathersError, name=BadRequest, code=400, className=bad-request, data="" errors=[message=uuid must be unique, type=unique violation, path=uuid, value=d87c40a9-fd67-45d8-a718-531cd81ab23b, origin=DB, id=null, uuid=d87c40a9-fd67-45d8-a718-531cd81ab23b, schema=1, commit=faf226350db4e8e09a39d81f7f361b665a5435f2 Apart from rollback, this case could even also happen if we decide to push a new UL that takes back a new plugin to a previous version, or even remove a plugin that got added for some testing phase (like what R. Tyler Croy did live during his DWJW2018 talk, showing a plugin, then removing it). Expected beh
[JIRA] (JENKINS-53964) Drop uuid_checksum_uniq unique key constraint
Title: Message Title Baptiste Mathus started work on JENKINS-53964 Change By: Baptiste Mathus Status: Open In Progress 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-53964) Drop uuid_checksum_uniq unique key constraint
Title: Message Title Baptiste Mathus assigned an issue to Baptiste Mathus Jenkins / JENKINS-53964 Drop uuid_checksum_uniq unique key constraint Change By: Baptiste Mathus Assignee: R. Tyler Croy Baptiste Mathus 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-53963) No login methods supported exception using Poll mailbox trigger plugin
Title: Message Title Sumit Bhardwaj created an issue Jenkins / JENKINS-53963 No login methods supported exception using Poll mailbox trigger plugin Issue Type: Bug Assignee: Nick Grealy Attachments: JenkinsError.PNG Components: poll-mailbox-trigger-plugin Created: 2018-10-09 17:35 Priority: Major Reporter: Sumit Bhardwaj Plugin version :: 1.026 Jenkins version :: 2.73.3 I have installed Poll-mailbox-trigger-plugin on my jenkins server. we are using MS-Exchange as a mail server. On clicking Test Connection we are getting following exception: Connecting to the mailbox... Error : javax.mail.MessagingException: No login methods supported!; nested exception is: com.sun.mail.iap.ProtocolException: No login methods supported! at com.sun.mail.imap.IMAPStore.protocolConnect(IMAPStore.java:663) at javax.mail.Service.connect(Service.java:295) at javax.mail.Service.connect(Service.java:176) at org.jenkinsci.plugins.pollmailboxtrigger.mail.MailReader.connect(MailReader.java:58) at org.jenkinsci.plugins.pollmailboxtrigger.PollMailboxTrigger.checkForEmails(PollMailboxTrigger.java:238) and sometime Connecting to the mailbox... Error : javax.mail.AuthenticationFailedException: AUTHENTICATE failed. at com.sun.mail.imap.IMAPStore.protocolConnect(IMAPStore.java:660) at javax.mail.Service.connect(Service.java:295) at javax.mail.Service.connect(Service.java:176) Please find the attached configuration screen-shot for reference.
[JIRA] (JENKINS-43758) Parameters disappear from pipeline job after running the job
Title: Message Title
Alexander Komarov edited a comment on JENKINS-43758
Re: Parameters disappear from pipeline job after running the job
I was managing to work around this issue by setting all properties I need at once in the properties{} closure (I generate jobs with Job DSL, and would rather have them set there). This was working fine, until I reached a *total blocker*: I cannot set the "Trigger builds remotely" token.-In other words, I generate a job that has the token set, but after running the job the token disappears, and *there is no pipeline DSL* for setting it.- Sorry, correction - even Job DSL plugin no longer handles "Trigger builds remotely" any more in pipelineJobs (seems to only apply to freestyleJob now), so it's not configurable either at generation time or at runtime by any means. I had to downgrade to Job DSL 1.69 due to this, see JENKINS-52743 Jenkins: 2.141, Pipeline-API: 2.29BTW: I am not using Declarative.
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-53250) Gerrit Trigger plugin compatibility with Jenkins As Code plugin (JEP-201)
Title: Message Title Paweł Kurek updated an issue Jenkins / JENKINS-53250 Gerrit Trigger plugin compatibility with Jenkins As Code plugin (JEP-201) Change By: Paweł Kurek Comment: Any news? @rsandell 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-53250) Gerrit Trigger plugin compatibility with Jenkins As Code plugin (JEP-201)
Title: Message Title Paweł Kurek commented on JENKINS-53250 Re: Gerrit Trigger plugin compatibility with Jenkins As Code plugin (JEP-201) Ewelina Wilkosz rsandell any news? 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-53250) Gerrit Trigger plugin compatibility with Jenkins As Code plugin (JEP-201)
Title: Message Title Paweł Kurek commented on JENKINS-53250 Re: Gerrit Trigger plugin compatibility with Jenkins As Code plugin (JEP-201) Any news? @rsandell 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-49570) Poll mail box plugin is not able to read the mail box of MS exchange but able to connect
Title: Message Title Sumit Bhardwaj commented on JENKINS-49570 Re: Poll mail box plugin is not able to read the mail box of MS exchange but able to connect hemant sharma I am not able to establish connection with MS exchange, I will highly appreciate if you could share details for the same 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-48420) Provide lightweight checkout capability for Subversion
Title: Message Title Philip Steiner commented on JENKINS-48420 Re: Provide lightweight checkout capability for Subversion Thanks Ivan I will forward the KB to my sys admin 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-48420) Provide lightweight checkout capability for Subversion
Title: Message Title Philip Steiner edited a comment on JENKINS-48420 Re: Provide lightweight checkout capability for Subversion Thanks Ivan [~ifernandezcalvo] I will forward the KB to my sys admin 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-43758) Parameters disappear from pipeline job after running the job
Title: Message Title
Nick Follett edited a comment on JENKINS-43758
Re: Parameters disappear from pipeline job after running the job
I am having this problem with declarative pipelines.{code:java}pipeline { agent any options {ansiColor('xterm')// Prevent multiple pipelines from running concurrently and failing due to tfstate lock filedisableConcurrentBuilds() } triggers {gitlab( branchFilterType: 'All', triggerOnPush: false, triggerOnMergeRequest: true, triggerOpenMergeRequestOnPush: "never", triggerOnNoteRequest: true, noteRegex: "jenkins rebuild", skipWorkInProgressMergeRequest: true,) } ...}{code}All of my pipelines are auto-imported from a separate job using the Job DSL plugin. I need to manually run each job once in order for the config.xml to be populated with the settings from the Jenkinsfile. When I check the configuration in the UI after this initial run I see that the pipeline is configured with the settings shown above. After I trigger the pipeline with a test merge request in GitLab the pipeline will succeed, but the trigger settings will disappear in the UI. If I trigger the job again manually the trigger settings for GitLab webhooks will re-appear. [ Jenkins ver. 2.107.3 |https://jenkins.io/] [~akom] I am having the same problem where I have 2 jobs which have their own version of the same pipeline, are both treated exactly the same, and one has this problem and the other does not. It's a very frustrating issue because it's inconsistent.
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-43758) Parameters disappear from pipeline job after running the job
Title: Message Title
Nick Follett edited a comment on JENKINS-43758
Re: Parameters disappear from pipeline job after running the job
I am having this problem with declarative pipelines.{code:java}pipeline { agent any options {ansiColor('xterm')// Prevent multiple pipelines from running concurrently and failing due to tfstate lock filedisableConcurrentBuilds() } triggers {gitlab( branchFilterType: 'All', triggerOnPush: false, triggerOnMergeRequest: true, triggerOpenMergeRequestOnPush: "never", triggerOnNoteRequest: true, noteRegex: "jenkins rebuild", skipWorkInProgressMergeRequest: true,) } ...}{code}All of my pipelines are auto-imported from a separate job using the Job DSL plugin. I need to manually run each job once in order for the config.xml to be populated with the settings from the Jenkinsfile. When I check the configuration in the UI after this initial run I see that the pipeline is configured with the settings shown above. After I trigger the pipeline with a test merge request in GitLab the pipeline will succeed, but the trigger settings will disappear in the UI. If I trigger the job again manually the trigger settings for GitLab webhooks will re-appear.[Jenkins ver. 2.107.3 |https://jenkins.io/] [~akom] I am having the same problem where I have 2 jobs which have their own version of the same pipeline, are both treated exactly the same, and one has this problem and the other does not. It's a very frustrating issue because it's inconsistent.
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-53962) Job DSL Support without Dynamic DSL
Title: Message Title Christoph Schulz created an issue Jenkins / JENKINS-53962 Job DSL Support without Dynamic DSL Issue Type: New Feature Assignee: Oleg Nenashev Components: build-name-setter-plugin Created: 2018-10-09 16:51 Labels: job-dsl Priority: Minor Reporter: Christoph Schulz build-name-setter currently only works in Job DSL due to Dynamic DSL which does not work, for example with the Job DSL Standalone generator. It would be nice if the plugin would support Job DSL officially. Thank you. Add Comment
[JIRA] (JENKINS-37588) Multibranch pipeline does not allow quiet time or throttle
Title: Message Title
John Muczynski commented on JENKINS-37588
Re: Multibranch pipeline does not allow quiet time or throttle
We do already use rate limiting (1 build at a time). Well, the Declarative Pipeline support might work for me. I'll have to get a new Jenkins version ... We're using multibranch pipelines.
pipeline {
agent any
options {| | | | quietPeriod(15)| | | | }
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://grou
[JIRA] (JENKINS-32867) Make build-name-setter-plugin compatible with Pipeline
Title: Message Title
Christoph Schulz commented on JENKINS-32867
Re: Make build-name-setter-plugin compatible with Pipeline
Tim Webster Note that Job DSL as no currentBuild* – Job DSL is executed for configuring the project, not the job. The equivalent for Job DSL is
buildNameUpdater {
buildName('whatever')
}
Howevery, build-name-setter only works due to Dynamic DSL, so in example the job-dsl-standalone generator would not work. * you could get a reference to a current build other ways, but that wouldn't be the build you want, it would be the Job DSL seed job.
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-53950) Support configuration as code
Title: Message Title Nicolas De Loof commented on JENKINS-53950 Re: Support configuration as code Root issue is CasC can't introspect "targets" type with non parameterized List argument to setTarget. proposed a potential fix here : https://github.com/jenkinsci/influxdb-plugin/pull/51 need concrete testing note: Plugin hasn't a Jenkinsfile to enable CI 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-53951) withMaven fail to set maven path when global variable is set
Title: Message Title
Bernardo Vale commented on JENKINS-53951
Re: withMaven fail to set maven path when global variable is set
Output attached. Executed with:
sh "env"
echo " with Maven ="
withMaven(jdk: 'JDK-8', maven: 'maven_3.5.3') {
sh "mvn help:system"
}
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-53951) withMaven fail to set maven path when global variable is set
Title: Message Title Bernardo Vale updated an issue Jenkins / JENKINS-53951 withMaven fail to set maven path when global variable is set Change By: Bernardo Vale Attachment: withmaven.txt 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-52907) Jenkins UI can be inaccessible if service is stopped while builds are in queue or running
Title: Message Title Fumiaki K commented on JENKINS-52907 Re: Jenkins UI can be inaccessible if service is stopped while builds are in queue or running To describe details on my error, I saw suspicious Jenkins behavior when I create a new folder. The folder seems to be created but GUI is freezed. Once going back to a top dir, then try accessng the folder, the error popped with the stack trace. The folder cannot be removed. My Jenkins was 30-min-old. Almost pure Jenkins 2.145. 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-53953) Downstream projects are not triggered if dependencies have a non null classifier
Title: Message Title Cyrille Le Clerc assigned an issue to Cyrille Le Clerc Jenkins / JENKINS-53953 Downstream projects are not triggered if dependencies have a non null classifier Change By: Cyrille Le Clerc Assignee: Alvaro Lobato Cyrille Le Clerc 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-53957) hpi bundles transitive dependencies of test scope dependencies
Title: Message Title James Nord commented on JENKINS-53957 Re: hpi bundles transitive dependencies of test scope dependencies Currently it is in a proprietary plugin. I will recreate in an OSS repo somewhere when I have time (but the code looked wrong to me when it does the filtering so I am supposed that this is not reproducible). 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-52907) Jenkins UI can be inaccessible if service is stopped while builds are in queue or running
Title: Message Title Matthew Smith commented on JENKINS-52907 Re: Jenkins UI can be inaccessible if service is stopped while builds are in queue or running Ok, I was just checking to see if your failure was the same as the one I posted. It might be, depending on which build gets corrupted the failure could be contained to a folder (I've seen that as well). When the job is not in a sub-folder and is instead in the top of the jobs folder that is when the entire UI is inaccessible 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-53951) withMaven fail to set maven path when global variable is set
Title: Message Title
Cyrille Le Clerc commented on JENKINS-53951
Re: withMaven fail to set maven path when global variable is set
Hello Bernardo Vale Can you please run something like the following and share the output?
sh "env"
echo " with Maven ="
withMaven(/* add the parameters you use*/) {
sh "mvn help:system"
}
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-52907) Jenkins UI can be inaccessible if service is stopped while builds are in queue or running
Title: Message Title Fumiaki K edited a comment on JENKINS-52907 Re: Jenkins UI can be inaccessible if service is stopped while builds are in queue or running Hi [~mksmith], no, my error pops when I access a folder, after logging in login . My error is about creating/accessing/deleting a folder. Oh, I mistook choosing a thread to post my error? 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-52907) Jenkins UI can be inaccessible if service is stopped while builds are in queue or running
Title: Message Title Fumiaki K commented on JENKINS-52907 Re: Jenkins UI can be inaccessible if service is stopped while builds are in queue or running Hi Matthew Smith, no, my error pops when I access a folder, after logging in. My error is about creating/accessing/deleting a folder. Oh, I mistook choosing a thread to post my error? 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-53951) withMaven fail to set maven path when global variable is set
Title: Message Title Cyrille Le Clerc assigned an issue to Cyrille Le Clerc Jenkins / JENKINS-53951 withMaven fail to set maven path when global variable is set Change By: Cyrille Le Clerc Assignee: Alvaro Lobato Cyrille Le Clerc 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-53942) Jobs using Artifactory plugin are disappeared post the plugin upgrade
Title: Message Title Pushkala Suriyanarayanan commented on JENKINS-53942 Re: Jobs using Artifactory plugin are disappeared post the plugin upgrade Hi Oleg, Matrix Project plugin 1.11 was installed and I updated to 1.13, but issue remains the same.. I can see the same error during startup.. Thank you!! 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-52907) Jenkins UI can be inaccessible if service is stopped while builds are in queue or running
Title: Message Title Matthew Smith commented on JENKINS-52907 Re: Jenkins UI can be inaccessible if service is stopped while builds are in queue or running Fumiaki K Did you see that error instead of the login screen after a restart of the Jenkins service as well? 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-52907) Jenkins UI can be inaccessible if service is stopped while builds are in queue or running
Title: Message Title Fumiaki K commented on JENKINS-52907 Re: Jenkins UI can be inaccessible if service is stopped while builds are in queue or running Same kind of error I met at Jenkins 2.145. Stack trace: org.apache.commons.jelly.JellyTagException: jar:file:/var/jenkins_home/war/WEB-INF/lib/jenkins-core-2.145.jar!/lib/hudson/actions.jelly:39:70: com/cloudbees/hudson/plugins/folder/properties/FolderCredentialsProviderorg.apache.commons.jelly.JellyTagException: jar:file:/var/jenkins_home/war/WEB-INF/lib/jenkins-core-2.145.jar!/lib/hudson/actions.jelly:39:70: com/cloudbees/hudson/plugins/folder/properties/FolderCredentialsProvider at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:745) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:289) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jell
[JIRA] (JENKINS-53961) Adding local jar file to hpi
Title: Message Title
jeff fairman created an issue
Jenkins / JENKINS-53961
Adding local jar file to hpi
Issue Type:
Task
Assignee:
Unassigned
Components:
maven-hpi-plugin
Created:
2018-10-09 15:20
Priority:
Major
Reporter:
jeff fairman
We have a Jenkins plugin - https://github.com/jenkinsci/nowsecure-auto-security-test-plugin that uses maven to build hpi file for plugin. I am adding a jar file that is locally available and I added dependency such as: com.nowsecure auto-plugin 0.4 system ${project.basedir}/lib/auto-plugin-0.4.jar But that jar file is not included in the hpi file despite adding it to target/dist/lib folder. Can you suggest best way to add this dependency so that it's included in the hpi file.
Add Comment
[JIRA] (JENKINS-46055) "dir" fails to use existing directory owned by root
Title: Message Title Jesse Glick assigned an issue to Unassigned Not a defect. You cannot run sh scripts from a directory to which you lack write access. Possibly FileMonitorController could be improved to fall back to a system temp directory of some kind for the durable task control directory, but at best you would be able to run read-only commands, which seems of limited value. Obviously if there is something you want to run with such a directory as your CWD, you can do so trivially via sh 'cd /go/src/github.com; ls -al' Jenkins / JENKINS-46055 "dir" fails to use existing directory owned by root Change By: Jesse Glick Issue Type: Bug Improvement Component/s: durable-task-plugin Component/s: kubernetes-plugin Component/s: workflow-basic-steps-plugin Assignee: Carlos Sanchez Add Comment
[JIRA] (JENKINS-45833) Can not spin up JNLP agent on Amazon ECS
Title: Message Title Jady Liu commented on JENKINS-45833 Re: Can not spin up JNLP agent on Amazon ECS Timothy Reaves, have you resolved the issue? 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-53810) Launch Agents fails with ERROR: null java.util.concurrent.CancellationException
Title: Message Title Jeff Thompson assigned an issue to Ivan Fernandez Calvo Jenkins / JENKINS-53810 Launch Agents fails with ERROR: null java.util.concurrent.CancellationException Change By: Jeff Thompson Assignee: Jeff Thompson Ivan Fernandez Calvo 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-53954) Cannot connect to slave/agent Linux anymore
Title: Message Title Jeff Thompson assigned an issue to Unassigned Jenkins / JENKINS-53954 Cannot connect to slave/agent Linux anymore Change By: Jeff Thompson Assignee: Jeff Thompson 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-49857) Provide easy single-sign-on by default with GitHub integration
Title: Message Title R. Tyler Croy stopped work on JENKINS-49857 Change By: R. Tyler Croy Status: In Progress Open 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-37588) Multibranch pipeline does not allow quiet time or throttle
Title: Message Title Jesse Glick commented on JENKINS-37588 Re: Multibranch pipeline does not allow quiet time or throttle Rate limiting is possible, though, as far as I know. 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-53959) Pipeline Git LFS avoid pull on Jenkins Master
Title: Message Title Mark Waite commented on JENKINS-53959 Re: Pipeline Git LFS avoid pull on Jenkins Master Extension plugin that allows optionally skipping LFS checkout on master seems like a reasonable approach in this case. A declarative Pipeline job (not multibranch) was assumed (by me anyway) that if it performs a checkout on the master (to get the Jenkinsfile, or for whatever other reason), it would use the same checkout as the agent uses. I'm not sure that my assumption was valid, only that it was my assumption. However, the GitHub Branch Source plugin, the Bitbucket Branch Source plugin, and the Gitea Branch Source plugin all use a REST API call to get the Jenkinsfile (for multibranch at least). If the purpose of the checkout on the master is just to obtain the Jenkinsfile, then I have no objection to an extension plugin that optionally skips LFS checkout on master. 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-53910) Ready-to-fly demo for simple PR job plugin
Title: Message Title Pham Vu Tuan closed an issue as Won't Do Jenkins / JENKINS-53910 Ready-to-fly demo for simple PR job plugin Change By: Pham Vu Tuan Status: Open Closed Resolution: Won't Do 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-53717) Keep extension point inside the plugin
Title: Message Title Pham Vu Tuan updated JENKINS-53717 Jenkins / JENKINS-53717 Keep extension point inside the plugin Change By: Pham Vu Tuan Status: In Review Resolved Resolution: Done 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-53959) Pipeline Git LFS avoid pull on Jenkins Master
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-53959 Pipeline Git LFS avoid pull on Jenkins Master Change By: Mark Waite Assignee: Mark Waite 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-37588) Multibranch pipeline does not allow quiet time or throttle
Title: Message Title Jesse Glick commented on JENKINS-37588 Re: Multibranch pipeline does not allow quiet time or throttle Was already implemented for Declarative Pipeline (JENKINS-51227), but is apparently not available in Scripted. 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-53736) JellyTagException for multibranch pipeline
Title: Message Title M W commented on JENKINS-53736 Re: JellyTagException for multibranch pipeline After updating the multi-branch with defaults plugin, this issue appears to be resolved. The new version is 2.0. The other mentioned plugins (and jenkins itself have not changed) 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-37588) Multibranch pipeline does not allow quiet time or throttle
Title: Message Title John Muczynski commented on JENKINS-37588 Re: Multibranch pipeline does not allow quiet time or throttle We have one project which needs a large quiet time while multiple commits are manually handled. But all the other projects have simple atomic commits. So we're in this battle of setting the global quiet time to 6 minutes vs 1 minute. So this feature would help. I'd run two Jenkins masters to solve the issue, but that hits other snags. We have several Jenkins worker machines that are needed for all these projects and the workers can't be shared among multiple masters. 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-45833) Can not spin up JNLP agent on Amazon ECS
Title: Message Title Jady Liu commented on JENKINS-45833 Re: Can not spin up JNLP agent on Amazon ECS Jan Roehrich, have you resolved the issue? I meet the same issue and still would not get it work. 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-38220) Support for EC2 instance profile credentials
Title: Message Title Kurt Madel commented on JENKINS-38220 Re: Support for EC2 instance profile credentials This should have been resolved with https://github.com/jenkinsci/aws-credentials-plugin/pull/20 - fixed since version 1.22 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-45787) AWS ECS slaves won't stay up
Title: Message Title Jady Liu commented on JENKINS-45787 Re: AWS ECS slaves won't stay up David Potter, I am having the exact same issue, have you got it work yet? 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-53867) Too many open files caused Jenkins crashed
Title: Message Title Tapio Reijonen updated an issue Jenkins / JENKINS-53867 Too many open files caused Jenkins crashed Change By: Tapio Reijonen Priority: Critical Blocker 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.
