[JIRA] (JENKINS-60958) [ASoC Plugin] While waiting for several scans to finish, 504 Gateway Timeout error returned from job
Title: Message Title
BAT-ULZII TSEND-OCHIR created an issue
Jenkins / JENKINS-60958
[ASoC Plugin] While waiting for several scans to finish, 504 Gateway Timeout error returned from job
Issue Type:
Bug
Assignee:
Matt Murphy
Attachments:
504_error.png, ScanRunning.png
Components:
ibm-asoc-plugin
Created:
2020-02-04 07:50
Environment:
Jenkins ver. 2.204.1 HCL AppScan plugin version 1.2.6
Labels:
plugin
Priority:
Major
Reporter:
BAT-ULZII TSEND-OCHIR
I'm using ASoC plugin from pipeline script like below reading scan targets from simple text file. Scan targets are about 90.
stage('Run ASoC static scan') {
when {
environment name: 'RUN_ASOC_SCAN', value: 'true'
}
steps {
echo "Will execute ASoC Static Scan"
script{
def projectNames = readFile 'asoc-scan-target-projects.txt'
def projects = projectNames.split("\n")
def failedProjects = []
for(int i = 0; i < projects.size(); i++) {
def project = projects[i]
def scanName = project.replaceAll("/", "-")
echo "Trying to run static scan of ${project}"
try{
appscan application: '##REDACTED###',
credentials: "${env.ASOC_CREDENTIAL}",
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Title: Message Title Pascal Widdershoven commented on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub -- Does not meet criteria Thanks for fixing this Liam Newman! It's been a long time frustration. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194753.1539776248000.723.1580801402732%40Atlassian.JIRA.
[JIRA] (JENKINS-60856) Breakpad Symbols are not uploaded properly
Title: Message Title Mez Pahlan commented on JENKINS-60856 Re: Breakpad Symbols are not uploaded properly Hi David Hodgkinson I'm going to look at this next. Here's the official docs for what you describe: https://docs.microsoft.com/en-gb/appcenter/diagnostics/android-ndk The only small complication vs the support we did for IOS is that I need to upload these symbols specifically as Breakpad symbols type as opposed to Android. With IOS / MacOS I could get away with simply Apple. But that's my problem Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204230.157986024.720.1580800980191%40Atlassian.JIRA.
[JIRA] (JENKINS-60171) HTTP 422 uploading Android APK artifact
Title: Message Title Mez Pahlan commented on JENKINS-60171 Re: HTTP 422 uploading Android APK artifact Terry Wallace yeah I've seen it a lot whilst Googling the error. I'll try and include some more debug information when we receive that type of error to get users to check these parameters. Let me know the change goes for you so I can update this priority accordingly. Many thanks! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203126.1573734069000.716.1580800560168%40Atlassian.JIRA.
[JIRA] (JENKINS-58249) Perforce plugin: JCasC cannot export configuration
Title: Message Title Joseph Petersen commented on JENKINS-58249 Re: Perforce plugin: JCasC cannot export configuration Paul Allen please consider adding configuration-as-code tests and updating credentials plugin to v2.2.0 or higher. Please read https://github.com/jenkinsci/configuration-as-code-plugin/blob/master/docs/PLUGINS.md Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200312.1561709954000.714.1580798040333%40Atlassian.JIRA.
[JIRA] (JENKINS-59247) "Fail if path is not found" property not working
Title: Message Title Ruslan Zhdanov edited a comment on JENKINS-59247 Re: "Fail if path is not found" property not working Is this issues not fully completed?[This| [https://github.com/jenkinsci/hashicorp-vault-plugin/blob/db6485286d5c0c5d3c6f1dc28677cb66500234da/src/main/java/com/datapipe/jenkins/vault/VaultBuildWrapper.java #L161]] does not support when vaultKey does not exist( () Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201710.1567692278000.709.1580796540202%40Atlassian.JIRA.
[JIRA] (JENKINS-59247) "Fail if path is not found" property not working
Title: Message Title Ruslan Zhdanov commented on JENKINS-59247 Re: "Fail if path is not found" property not working Is this issues not fully completed? This does not support when vaultKey does not exist( () Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201710.1567692278000.706.1580796480214%40Atlassian.JIRA.
[JIRA] (JENKINS-50331) JENKINS -Error Message:FATAL: null java.lang.StackOverflowError at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListen
Title: Message Title Allan BURDAJEWICZ edited a comment on JENKINS-50331 Re: JENKINS -Error Message:FATAL: null java.lang.StackOverflowError at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListen I also found http://blogs.pitx3.com/2016/01/24/mulesoft-microsoft-java-tfs-stackoverflowerror/. This user has reached out to Microsoft and while they did not confirm it was a bug they provided him with a workaround. It is mentioned in the release note that Stackoverlflow issue is solved in https://github.com/microsoft/team-explorer-everywhere/releases/tag/v14.0.3. If we have a look at [the source code of the SDK|https://github.com/microsoft/team-explorer-everywhere/blob/releases/14.0.3/source/com.microsoft.tfs.core/src/com/microsoft/tfs/core/TFSTeamProjectCollection.java#L261-L276]) however, the TFSConfigurationServer is closed after the TFSTeamProjectCollection and (while the workaround is to close it before).We can see that the TFS plugin [does already this in a way|https://github.com/jenkinsci/tfs-plugin/blob/tfs-5.157.0/tfs/src/main/java/hudson/plugins/tfs/model/Server.java#L274-L290]. But there is some legacy code using reflection that could be cleaned up. Proposed https://github.com/jenkinsci/tfs-plugin/pull/230 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-
[JIRA] (JENKINS-60957) Plot Data graphs - Need to change the Legends name
Title: Message Title Chandrakumar Sekar created an issue Jenkins / JENKINS-60957 Plot Data graphs - Need to change the Legends name Issue Type: Bug Assignee: Silk Performer Attachments: image-2020-02-04-04-06-25-686.png Components: core, silk-performer-plugin Created: 2020-02-04 04:07 Environment: Jenkins 2.190, Silk Performer 20.5, JDK 1.8 Labels: plot SilkPerformerPlotData SilkPerformer20.5 Priority: Major Reporter: Chandrakumar Sekar Hello, I have been plotting data from the file - OverviewReport.xml generated by Silk Performance Explorer, i.e. Plotting the Total Transaction Vs Error Rate for each build in Jenkins post completion of my performance test, but i am facing an issue where the Legends are coming same as xml node value from above mentioned xml and it the makes the difficult to understand for the persons viewing the graph, for example, the total transaction fetched from xml node value Sumcount1 and Error transactions are from xml node Value and the same is appearing in the graph as well, so can you please advise if this legends value can be customized to make the plot more descriptive? Please refer the highlighted legends in the image where i need to customize with meaningful description.
[JIRA] (JENKINS-50331) JENKINS -Error Message:FATAL: null java.lang.StackOverflowError at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListen
Title: Message Title Allan BURDAJEWICZ edited a comment on JENKINS-50331 Re: JENKINS -Error Message:FATAL: null java.lang.StackOverflowError at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListen I also found http://blogs.pitx3.com/2016/01/24/mulesoft-microsoft-java-tfs-stackoverflowerror/. This user has reached out to Microsoft and while they did not confirm it was a bug they provided him with a workaround. I It is mentioned in the release note that Stackoverlflow issue is solved in https://github.com/microsoft/team-explorer-everywhere/releases/tag/v14.0.3. If we have a look at [the source code of the SDK|https://github.com/microsoft/team-explorer-everywhere/blob/releases/14.0.3/source/com.microsoft.tfs.core/src/com/microsoft/tfs/core/TFSTeamProjectCollection.java#L261-L276]) however, the TFSConfigurationServer is closed after the TFSTeamProjectCollection and (while the workaround is to close it before).We can see that the TFS plugin [does already this in a way|https://github.com/jenkinsci/tfs-plugin/blob/tfs-5.157.0/tfs/src/main/java/hudson/plugins/tfs/model/Server.java#L274-L290]. But there is some legacy code using reflection that could be cleaned up. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189378.1521699501000.677.1580787720400%40
[JIRA] (JENKINS-50331) JENKINS -Error Message:FATAL: null java.lang.StackOverflowError at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListen
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-50331 Re: JENKINS -Error Message:FATAL: null java.lang.StackOverflowError at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListen I also found http://blogs.pitx3.com/2016/01/24/mulesoft-microsoft-java-tfs-stackoverflowerror/. This user has reached out to Microsoft and while they did not confirm it was a bug they provided him with a workaround. I can see that the TFS plugin does already this in a way. But there is some legacy code using reflection that could be cleaned up. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189378.1521699501000.662.1580784960422%40Atlassian.JIRA.
[JIRA] (JENKINS-60956) Build statuses not displaying for multiple jobs
Title: Message Title Martin Henschke updated an issue Jenkins / JENKINS-60956 Build statuses not displaying for multiple jobs Change By: Martin Henschke Summary: Build statuses not working displaying for multiple jobs Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204416.158077623.659.1580777640071%40Atlassian.JIRA.
[JIRA] (JENKINS-55220) Multibranch Pipeline jobs get randomly lost
Title: Message Title Morgan Robertson edited a comment on JENKINS-55220 Re: Multibranch Pipeline jobs get randomly lost This seems similar The following are issues that I believe are duplicates or are related to this: https://issues.jenkins-ci.org/browse/JENKINS-55388 https://issues.jenkins-ci.org/browse/JENKINS-57848https://issues.jenkins-ci.org/browse/JENKINS-57398https://issues.jenkins-ci.org/browse/JENKINS-57381 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196298.154504211.643.1580777220390%40Atlassian.JIRA.
[JIRA] (JENKINS-55220) Multibranch Pipeline jobs get randomly lost
Title: Message Title Morgan Robertson commented on JENKINS-55220 Re: Multibranch Pipeline jobs get randomly lost This seems similar to https://issues.jenkins-ci.org/browse/JENKINS-55388 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196298.154504211.626.1580776920357%40Atlassian.JIRA.
[JIRA] (JENKINS-55388) multibranch pipeline deleting history and building unexpectedly
Title: Message Title Morgan Robertson commented on JENKINS-55388 Re: multibranch pipeline deleting history and building unexpectedly This seems very similar to https://issues.jenkins-ci.org/browse/JENKINS-55220 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196496.1546519053000.612.1580776860676%40Atlassian.JIRA.
[JIRA] (JENKINS-60956) Build statuses not working for multiple jobs
Title: Message Title Martin Henschke created an issue Jenkins / JENKINS-60956 Build statuses not working for multiple jobs Issue Type: Bug Assignee: Martin Henschke Components: atlassian-bitbucket-server-integration-plugin Created: 2020-02-04 00:30 Environment: Jenkins 2.164 Priority: Major Reporter: Martin Henschke Build statuses are currently identified simply as an integer, with no differentiation between jobs. This leads to only one job's build status actually being visible in Bitbucket Server. Steps to replicate: Create two projects for two separate repositories in Bitbucket Server Run a build for each project once Expected result: Both commits have a build status visible in Bitbucket Server Actual result: Only one commit has a build status Add Comment
[JIRA] (JENKINS-60392) Allow environment variables with Bitbucket Server Integration Pipeline
Title: Message Title
Martin Henschke commented on JENKINS-60392
Re: Allow environment variables with Bitbucket Server Integration Pipeline
Hi Bruce, I wasn't able to reproduce this issue. I created an environment table similar to [this|https://jenkins.io/doc/pipeline/tour/environment/,] and the variable was substituted correctly. I notice in your example, you use single quotes- which when I did would attempt to scan for a branch named literally named ${ENV_VARNAME}, but with double quotes, the name was correctly substituted. Could you possibly provide a more complete Jenkinsfile and a snippet from the build logs, so we can investigate further?
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203446.157565559.604.1580774100302%40Atlassian.JIRA.
[JIRA] (JENKINS-60392) Allow environment variables with Bitbucket Server Integration Pipeline
Title: Message Title
Martin Henschke edited a comment on JENKINS-60392
Re: Allow environment variables with Bitbucket Server Integration Pipeline
Hi Bruce,I wasn't able to reproduce this issue. I created an environment table similar to [ this|[ https://jenkins.io/doc/pipeline/tour/environment/] ,] and the variable was substituted correctly. I notice in your example, you use single quotes- which when I did would attempt to scan for a branch named literally named ${ENV_VARNAME}, but with double quotes, the name was correctly substituted.Could you possibly provide a more complete Jenkinsfile and a snippet from the build logs, so we can investigate further?
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203446.157565559.608.1580774100386%40Atlassian.JIRA.
[JIRA] (JENKINS-60809) No GIT_* environment entries set during pipeline run
Title: Message Title Martin Henschke started work on JENKINS-60809 Change By: Martin Henschke Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204140.1579280474000.601.1580770320636%40Atlassian.JIRA.
[JIRA] (JENKINS-60809) No GIT_* environment entries set during pipeline run
Title: Message Title Martin Henschke assigned an issue to Martin Henschke Jenkins / JENKINS-60809 No GIT_* environment entries set during pipeline run Change By: Martin Henschke Assignee: Kristy Hughes Martin Henschke Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204140.1579280474000.599.1580770320542%40Atlassian.JIRA.
[JIRA] (JENKINS-60171) HTTP 422 uploading Android APK artifact
Title: Message Title
Terry Wallace edited a comment on JENKINS-60171
Re: HTTP 422 uploading Android APK artifact
no I'm sure its not the case. Here is the jenkins script EDIT:(On reading the second link you sent..I'm not so sure.. that could indeed be the case.. Thats a terrible design on there part to use a single endpoint and change the name of the app behind the scenes on you. I'll try appending the -1 to the android uploads... makes me wonder if you made a windows universal app first would your ios be -1 and your android -2 ? ) def uploadBundleToAppCenter(bundle, appenv) { def pipeline = new com.company.jenkins.PipelineUtils(); withCredentials([string(credentialsId: 'appcenter_token_default', variable: 'APPCENTER_API_TOKEN')]) { p1 = bundle.outputPath; p2 = WORKSPACE; p3 = p1[p1.indexOf(p2)+p2.length()+1..-1]; p4 = 'client/Assets/Appconfigs/../../../' appPath = p3[p3.indexOf(p4)+p4.length()+1..-1]; dbgPath = null if (appPath.indexOf('.ipa')>0) { { dbgPath = appPath.replaceAll(/\.ipa$/, '.dSYM.zip') } //Add other tests here if need to add other debug symbols.appCenter apiToken: APPCENTER_API_TOKEN, appName: 'name_'+appenv, //currently hardcoded. UNtil rewrite. distributionGroups: bundle.hockeyapp.teams, ownerName: '*Actual owner name removed', notifyTesters: false, pathToApp: appPath, pathToDebugSymbols: dbgPath, releaseNotes: bundle.hockeyapp.releaseNotes;} } and the only thing built and passed to this is the name of the .ipa or the .apkas you can see from my earlier post it says "File found matching pattern: build/client/Dingo_google_universal_enterprise.apk"and I can browse to that file and upload to appcenter directly and it works.The P1-P4 strings are just to trim the extra long workspace paths to direct /subdirectory paths below the client.appPath is build/client/Dingo_google_universal_enterprise.apk"dbgPath = null.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-51519) GitHub Organization should allow skipping archived repositories
Title: Message Title Liam Newman assigned an issue to Unassigned Jenkins / JENKINS-51519 GitHub Organization should allow skipping archived repositories Change By: Liam Newman Assignee: Kohsuke Kawaguchi Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190897.152715431.561.1580768100709%40Atlassian.JIRA.
[JIRA] (JENKINS-51519) GitHub Organization should allow skipping archived repositories
Title: Message Title Liam Newman closed an issue as Fixed https://github.com/jenkinsci/github-branch-source-plugin/releases/tag/github-branch-source-2.6.0 Jenkins / JENKINS-51519 GitHub Organization should allow skipping archived repositories Change By: Liam Newman Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190897.152715431.541.1580768041687%40Atlassian.JIRA.
[JIRA] (JENKINS-51519) GitHub Organization should allow skipping archived repositories
Title: Message Title Liam Newman assigned an issue to Kohsuke Kawaguchi Jenkins / JENKINS-51519 GitHub Organization should allow skipping archived repositories Change By: Liam Newman Assignee: Nik Reiman Kohsuke Kawaguchi Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190897.152715431.551.1580768042140%40Atlassian.JIRA.
[JIRA] (JENKINS-51519) GitHub Organization should allow skipping archived repositories
Title: Message Title Liam Newman assigned an issue to Nik Reiman Jenkins / JENKINS-51519 GitHub Organization should allow skipping archived repositories Change By: Liam Newman Assignee: Kohsuke Kawaguchi Nik Reiman Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190897.152715431.539.1580768041663%40Atlassian.JIRA.
[JIRA] (JENKINS-60413) Regression: Branch scanning fails when PR refer to a deleted fork
Title: Message Title Liam Newman commented on JENKINS-60413 Re: Regression: Branch scanning fails when PR refer to a deleted fork https://github.com/jenkinsci/github-branch-source-plugin/releases/tag/github-branch-source-2.6.0 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203470.157594813.523.1580767980337%40Atlassian.JIRA.
[JIRA] (JENKINS-60171) HTTP 422 uploading Android APK artifact
Title: Message Title
Terry Wallace commented on JENKINS-60171
Re: HTTP 422 uploading Android APK artifact
no I'm sure its not the case. Here is the jenkins script def uploadBundleToAppCenter(bundle, appenv) { def pipeline = new com.company.jenkins.PipelineUtils(); withCredentials([string(credentialsId: 'appcenter_token_default', variable: 'APPCENTER_API_TOKEN')]) { p1 = bundle.outputPath; p2 = WORKSPACE; p3 = p1[p1.indexOf(p2)+p2.length()+1..-1]; p4 = 'client/Assets/Appconfigs/../../../' appPath = p3[p3.indexOf(p4)+p4.length()+1..-1]; dbgPath = null if (appPath.indexOf('.ipa')>0) { dbgPath = appPath.replaceAll(/\.ipa$/, '.dSYM.zip') } //Add other tests here if need to add other debug symbols. appCenter apiToken: APPCENTER_API_TOKEN, appName: 'name_'+appenv, //currently hardcoded. UNtil rewrite. distributionGroups: bundle.hockeyapp.teams, ownerName: '*Actual owner name removed', notifyTesters: false, pathToApp: appPath, pathToDebugSymbols: dbgPath, releaseNotes: bundle.hockeyapp.releaseNotes; } } and the only thing built and passed to this is the name of the .ipa or the .apk as you can see from my earlier post it says "File found matching pattern: build/client/Dingo_google_universal_enterprise.apk" and I can browse to that file and upload to appcenter directly and it works. The P1-P4 strings are just to trim the extra long workspace paths to direct /subdirectory paths below the client. appPath is build/client/Dingo_google_universal_enterprise.apk" dbgPath = null.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues"
[JIRA] (JENKINS-60413) Regression: Branch scanning fails when PR refer to a deleted fork
Title: Message Title Liam Newman closed an issue as Fixed Jenkins / JENKINS-60413 Regression: Branch scanning fails when PR refer to a deleted fork Change By: Liam Newman Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203470.157594813.529.1580767980473%40Atlassian.JIRA.
[JIRA] (JENKINS-60413) Regression: Branch scanning fails when PR refer to a deleted fork
Title: Message Title Liam Newman updated JENKINS-60413 Jenkins / JENKINS-60413 Regression: Branch scanning fails when PR refer to a deleted fork Change By: Liam Newman Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203470.157594813.521.1580767920375%40Atlassian.JIRA.
[JIRA] (JENKINS-49259) Support team dimension in GitHub
Title: Message Title Liam Newman commented on JENKINS-49259 Re: Support team dimension in GitHub Thanks sundeep kahlon ! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188116.1517321943000.516.1580767860773%40Atlassian.JIRA.
[JIRA] (JENKINS-49259) Support team dimension in GitHub
Title: Message Title Liam Newman closed an issue as Fixed Jenkins / JENKINS-49259 Support team dimension in GitHub Change By: Liam Newman Status: In Progress Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188116.1517321943000.514.1580767860743%40Atlassian.JIRA.
[JIRA] (JENKINS-59039) Add switch for choose `checkApiRateLimit` implementation
Title: Message Title Liam Newman closed an issue as Fixed Jenkins / JENKINS-59039 Add switch for choose `checkApiRateLimit` implementation Change By: Liam Newman Status: Open Closed Resolution: Fixed Released As: https://github.com/jenkinsci/github-branch-source-plugin/releases/tag/github-branch-source-2.6.0 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201393.1566424256000.509.1580767800153%40Atlassian.JIRA.
[JIRA] (JENKINS-60353) Non-mergable Pull-request Contents Get into GH Cache with False-Positive 404
Title: Message Title Liam Newman updated JENKINS-60353 Jenkins / JENKINS-60353 Non-mergable Pull-request Contents Get into GH Cache with False-Positive 404 Change By: Liam Newman Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203370.1575386738000.506.1580767680672%40Atlassian.JIRA.
[JIRA] (JENKINS-60353) Non-mergable Pull-request Contents Get into GH Cache with False-Positive 404
Title: Message Title Liam Newman commented on JENKINS-60353 Re: Non-mergable Pull-request Contents Get into GH Cache with False-Positive 404 Vladimir Kuklin Github-branch-source-plugin v2.6.0 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203370.1575386738000.503.1580767680555%40Atlassian.JIRA.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Title: Message Title Liam Newman updated JENKINS-54126 Github-branch-source-plugin v2.6.0 Jenkins / JENKINS-54126 Jenkinsfile not found in PR on GitHub -- Does not meet criteria Change By: Liam Newman Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194753.1539776248000.398.1580767625909%40Atlassian.JIRA.
[JIRA] (JENKINS-60171) HTTP 422 uploading Android APK artifact
Title: Message Title Mez Pahlan commented on JENKINS-60171 Re: HTTP 422 uploading Android APK artifact Is your situation similar to this comment: https://github.com/microsoft/fastlane-plugin-appcenter/issues/111#issuecomment-526710094 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203126.1573734069000.394.1580767020166%40Atlassian.JIRA.
[JIRA] (JENKINS-60171) HTTP 422 uploading Android APK artifact
Title: Message Title Mez Pahlan commented on JENKINS-60171 Re: HTTP 422 uploading Android APK artifact Wait.. hang about does this help: https://github.com/microsoft/fastlane-plugin-appcenter/issues/111 Can you check that when you invoke your script / pipeline configuration to upload your Android app that you're not accidently trying to upload to the IOS version of your project in AppCenter like the user in that Fastlane issue was. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203126.1573734069000.390.1580766900185%40Atlassian.JIRA.
[JIRA] (JENKINS-60171) HTTP 422 uploading Android APK artifact
Title: Message Title Mez Pahlan commented on JENKINS-60171 Re: HTTP 422 uploading Android APK artifact Hi Terry Wallace thanks so much for that. Can you post your pipeline configuration please. Obviously redact anything sensitive. > If you are setting a platform type in the background, how are you ascertaining the type ? We only try and ascertain the platform type for the debug symbols because we need to pass an enum type for the platform to satisfy the API for debug symbols. However if that were failing I would expect the stack trace to have lines referencing "Upload symbols to resource unsuccessful:". Instead it has a reference to "Upload app to resource unsuccessful:". We don't need to specify the platform for the main app upload (as best as I remember). My initial suspicion is that for some reason the upload URL that was used to successfully upload your IOS app is trying to be used to upload the Android app. Might be clearer when you repost your pipeline configuration in full. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203126.1573734069000.386.1580766480196%40Atlassian.JIRA.
[JIRA] (JENKINS-45504) Add @Symbol annotations to traits
Title: Message Title René Scheibe closed an issue as Fixed Jenkins / JENKINS-45504 Add @Symbol annotations to traits Change By: René Scheibe Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183680.1499933648000.384.1580766368911%40Atlassian.JIRA.
[JIRA] (JENKINS-45504) Add @Symbol annotations to traits
Title: Message Title René Scheibe updated JENKINS-45504 Jenkins / JENKINS-45504 Add @Symbol annotations to traits Change By: René Scheibe Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183680.1499933648000.351.1580766368455%40Atlassian.JIRA.
[JIRA] (JENKINS-45504) Add @Symbol annotations to traits
Title: Message Title René Scheibe commented on JENKINS-45504 Re: Add @Symbol annotations to traits Now a release for each of the 3 plugins has been performed that contains the relevant changes. Thanks everybody. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183680.1499933648000.285.1580766367569%40Atlassian.JIRA.
[JIRA] (JENKINS-45504) Add @Symbol annotations to traits
Title: Message Title René Scheibe updated JENKINS-45504 Jenkins / JENKINS-45504 Add @Symbol annotations to traits Change By: René Scheibe Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183680.1499933648000.318.1580766367989%40Atlassian.JIRA.
[JIRA] (JENKINS-45504) Add @Symbol annotations to traits
Title: Message Title René Scheibe updated an issue Jenkins / JENKINS-45504 Add @Symbol annotations to traits Change By: René Scheibe Released As: git-plugin 4.0.0, bitbucket-branch-source-plugin 2.7.0, github-branch-source-plugin TODO 2.6.0 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183680.1499933648000.221.1580766241696%40Atlassian.JIRA.
[JIRA] (JENKINS-60950) Differences between PreBuildMerge and MergeWithSCMExtention
Title: Message Title Mark Waite closed an issue as Not A Defect Closed as "Not a defect" Jenkins / JENKINS-60950 Differences between PreBuildMerge and MergeWithSCMExtention Change By: Mark Waite Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.go
[JIRA] (JENKINS-50219) Jenkins agent windows service fails to restart with an unhandled COMException in WinSw's log
Title: Message Title Angelo Loria commented on JENKINS-50219 Re: Jenkins agent windows service fails to restart with an unhandled COMException in WinSw's log Tom Manning added a comment - 2018-05-24 05:47 After some further investigation I believe I have found a more permanent work around for the problem. After observing that the problem occurs when the master is restarted after logging out from an interactive session on the "Log On As" account that runs the Jenkins agent service. The fix is to enable the group policy setting "Local Computer Policy->Administrative Templates->System->User Profiles->Do not forcefully unload the users registry at user logoff". FYI this resolved the issue for us on a Windows Server 2019 VM. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189243.1521208116000.203.1580762160347%40Atlassian.JIRA.
[JIRA] (JENKINS-60950) Differences between PreBuildMerge and MergeWithSCMExtention
Title: Message Title Mark Waite commented on JENKINS-60950 Re: Differences between PreBuildMerge and MergeWithSCMExtention Please don't use bug reports to ask questions. Bug reports are monitored by very few volunteers. Mailing lists and chat channels are monitored by many more volunteers. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204352.1580735353000.201.1580761020218%40Atlassian.JIRA.
[JIRA] (JENKINS-56194) Not able to run UFT ALM Scripts from master when the slave machine is logged off
Title: Message Title Mat Walker commented on JENKINS-56194 Re: Not able to run UFT ALM Scripts from master when the slave machine is logged off Sakti, FYI Daniel Gront We have this issue with Bamboo (we are migrating to Jenkins) so I confirm it is NOT Jenkins. To resolve, you need to; Log on to Test Execution host machine. Launch UFT In Tools->Options click ‘Verify Connection’ button Close UFT Disconnect from Test Execution host machine (DO NOT LOG OFF!) Apparently ALM has had this issue since QC (Quality Centre days). Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197744.1550569008000.199.1580759760312%40Atlassian.JIRA.
[JIRA] (JENKINS-60955) Jira Trigger plugin doesn't load
Title: Message Title Sathish Kumar updated an issue Jenkins / JENKINS-60955 Jira Trigger plugin doesn't load Change By: Sathish Kumar * .783+ [id=237] WARNING h.ExtensionFinder$GuiceFinder$SezpozModule#configure: Failed to load com.ceilfors.jenkins.plugins.jiratrigger.JiraCommentTrigger$JiraCommentTriggerDescriptor * * java.lang.NullPointerException * at hudson.ExtensionFinder$GuiceFinder$SezpozModule.resolve(ExtensionFinder.java:504) * Caused: java.lang.LinkageError: Failed to resolve interface com.ceilfors.jenkins.plugins.jiratrigger.jira.JiraClient * at hudson.ExtensionFinder$GuiceFinder$SezpozModule.resolve(ExtensionFinder.java:516) at hudson.ExtensionFinder$GuiceFinder$SezpozModule.resolve(ExtensionFinder.java:510) at hudson.ExtensionFinder$GuiceFinder$SezpozModule.resolve(ExtensionFinder.java:487) at hudson.ExtensionFinder$GuiceFinder$SezpozModule.configure(ExtensionFinder.java:536) at com.google.inject.AbstractModule.configure(AbstractModule.java:62) at com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:340) at com.google.inject.spi.Elements.getElements(Elements.java:110) at com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:138) at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:104) at com.google.inject.internal.InjectorImpl.createChildInjector(InjectorImpl.java:226) at hudson.ExtensionFinder$GuiceFinder.refresh(ExtensionFinder.java:347) at jenkins.model.Jenkins.refreshExtensions(Jenkins.java:2698) at hudson.PluginManager.start(PluginManager.java:975) at hudson.model.UpdateCenter$CompleteBatchJob.run(UpdateCenter.java:2245) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:111) at java.lang.Thread.run(Thread.java:748)2020-02-03 19:21:56.849+ [id=240] INFO jenkins.InitReactorRunner$1#onAttained: Started initialization2020-02-03 19:21:56.850+ [id=245] INFO jenkins.InitReactorRunner$1#onAttained: Listed all plugins Add Comment
[JIRA] (JENKINS-60955) Jira Trigger plugin doesn't load
Title: Message Title Sathish Kumar created an issue Jenkins / JENKINS-60955 Jira Trigger plugin doesn't load Issue Type: Bug Assignee: Wisen Tanasa Components: jira-trigger-plugin Created: 2020-02-03 19:40 Environment: -rhel7 -jenkins 2.214 -jira-trigger 1.0.0 Priority: Blocker Reporter: Sathish Kumar .783+ [id=237] WARNING h.ExtensionFinder$GuiceFinder$SezpozModule#configure: Failed to load com.ceilfors.jenkins.plugins.jiratrigger.JiraCommentTrigger$JiraCommentTriggerDescriptor java.lang.NullPointerException at hudson.ExtensionFinder$GuiceFinder$SezpozModule.resolve(ExtensionFinder.java:504) Caused: java.lang.LinkageError: Failed to resolve interface com.ceilfors.jenkins.plugins.jiratrigger.jira.JiraClient at hudson.ExtensionFinder$GuiceFinder$SezpozModule.resolve(ExtensionFinder.java:516) at hudson.ExtensionFinder$GuiceFinder$SezpozModule.resolve(ExtensionFinder.java:510) at hudson.ExtensionFinder$GuiceFinder$SezpozModule.resolve(ExtensionFinder.java:487) at hudson.ExtensionFinder$GuiceFinder$SezpozModule.configure(ExtensionFinder.java:536) at com.google.inject.AbstractModule.configure(AbstractModule.java:62) at com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:340) at com.google.inject.spi.Elements.getElements(Elements.java:110) at com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:138) at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:104) at com.google.inject.internal.InjectorImpl.createChildInjector(InjectorImpl.java:226) at hudson.ExtensionFinder$GuiceFinder.refresh(ExtensionFinder.java:347) at jenkins.model.Jenkins.refreshExtensions(Jenkins.java:2698) at hudson.PluginManager.start(PluginManager.java:975) at hudson.model.UpdateCenter$CompleteBatchJob.run(UpdateCenter.java:22
[JIRA] (JENKINS-60954) credential displayName for StringCredential uses description only
Title: Message Title Dennis Chang created an issue Jenkins / JENKINS-60954 credential displayName for StringCredential uses description only Issue Type: Improvement Assignee: Unassigned Attachments: Screen Shot 2020-01-21 at 1.42.40 PM.png, Screen Shot 2020-01-21 at 1.43.00 PM.png Components: plain-credentials-plugin Created: 2020-02-03 19:39 Environment: Jenkins LTS version 2.176.4, plain credential plugin version 1.5 Labels: credentials Priority: Minor Reporter: Dennis Chang After creating a SecretText credential, the displayName of the credential uses the Description field only and does not use the ID of the credential as part of the displayName. See part of code here: https://github.com/jenkinsci/plain-credentials-plugin/blob/83be2ca41c6c5e6f96eb6c9a47ebdd394b2a6dbc/src/main/java/org/jenkinsci/plugins/plaincredentials/StringCredentials.java#L52-L54
[JIRA] (JENKINS-60884) NPE in hudson.model.Run.getPreviousBuildsOverThreshold
Title: Message Title Tim Jacomb updated JENKINS-60884 Jenkins / JENKINS-60884 NPE in hudson.model.Run.getPreviousBuildsOverThreshold Change By: Tim Jacomb Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204271.158016016.187.1580758020827%40Atlassian.JIRA.
[JIRA] (JENKINS-60884) NPE in hudson.model.Run.getPreviousBuildsOverThreshold
Title: Message Title Tim Jacomb started work on JENKINS-60884 Change By: Tim Jacomb Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204271.158016016.184.1580758020725%40Atlassian.JIRA.
[JIRA] (JENKINS-60884) NPE in hudson.model.Run.getPreviousBuildsOverThreshold
Title: Message Title Tim Jacomb commented on JENKINS-60884 Re: NPE in hudson.model.Run.getPreviousBuildsOverThreshold https://github.com/jenkinsci/jenkins/pull/4471 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204271.158016016.190.1580758020877%40Atlassian.JIRA.
[JIRA] (JENKINS-60884) NPE in hudson.model.Run.getPreviousBuildsOverThreshold
Title: Message Title Tim Jacomb assigned an issue to Aaron Zurawski Jenkins / JENKINS-60884 NPE in hudson.model.Run.getPreviousBuildsOverThreshold Change By: Tim Jacomb Assignee: Aaron Zurawski Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204271.158016016.181.1580758020655%40Atlassian.JIRA.
[JIRA] (JENKINS-44450) Block scoped usage
Title: Message Title Ulli Hafner commented on JENKINS-44450 Re: Block scoped usage What do you want to comment? This issue? Then just continue in Jira. Or would you like to ask generic questions? Then please use the Gitter channel. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182278.1495543785000.171.1580757060334%40Atlassian.JIRA.
[JIRA] (JENKINS-60949) [EnvInject] Injecting properties of previous build breaks SCM polling
Title: Message Title Sebastian Ratz updated an issue Jenkins / JENKINS-60949 [EnvInject] Injecting properties of previous build breaks SCM polling Change By: Sebastian Ratz The EnvInject plugin re-injects the environment of the previous build into the SCM poll for the next build.However, it does this blindly, without considering when and where the previous build happened, and without knowing if the properties are actually applicable.Scenario: # Have 2 slaves (*slave-linux*, *slave-windows*) # Configure job for SCM polling # Build job for the first time -> runs on *slave-linux* ** # builds/1/injectedEnvVars.txt contains, for example, *HOME=/home/jenkins* # ** Wait for next SCM poll. # SCM poll runs on *slave-windows* this time. # EnvInject blindly takes the env vars from injectedEnvVars.txt from build 1 and injects it into the SCM polling process. # SCM polling on Windows fails, e.g. with "Could not create directory '/home/jenkins/.ssh'." because of the wrong *HOME* environment variable.Is there a way to prevent this? The job in question does not even make use of the EnvInject functionality, yet, injecting still happens at SCM polling time. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59705) hudson.remoting.ChannelClosedException: Channel "unknown": Remote call on JNLP4-connect connection from IP/IP:58344 failed. The channel is closing down or has closed dow
Title: Message Title
Joe Roberts commented on JENKINS-59705
Re: hudson.remoting.ChannelClosedException: Channel "unknown": Remote call on JNLP4-connect connection from IP/IP:58344 failed. The channel is closing down or has closed dow
I'm having the same random issue: Jenkins master version: 2.204.2 Kubernetes Plugin: 1.23.2 Pod Spec
"name": "jnlp",
"resources": {
"limits": {
"cpu": "800m",
"memory": "1Gi"
},
"requests": {
"cpu": "800m",
"memory": "1Gi"
}
},
Master
2020-02-03 16:41:28.091+ [id=8198] INFO j.s.DefaultJnlpSlaveReceiver#channelClosed: IOHub#1: Worker[channel:java.nio.channels.SocketChannel[connected local=/10.15.199.33:5 remote=10.15.198.22/10.15.198.22:39686]] / Computer.threadPoolForRemoting [#2516] for default-jsnmd terminated: java.nio.channels.ClosedChannelException
Slave
INFO: ConnectedINFO: ConnectedFeb 03, 2020 1:49:45 PM org.eclipse.jgit.util.FS$FileStoreAttributes saveToConfigWARNING: locking FileBasedConfig[/home/jenkins/.config/jgit/config] failed after 5 retriesFeb 03, 2020 4:41:28 PM hudson.remoting.jnlp.Main$CuiListener statusINFO: TerminatedFeb 03, 2020 4:41:28 PM hudson.Launcher$RemoteLaunchCallable$1 joinINFO: Failed to synchronize IO streams on the channel hudson.remoting.Channel@5e672cca:JNLP4-connect connection to jenkins-agent/10.15.54.222:5hudson.remoting.ChannelClosedException: Channel "hudson.remoting.Channel@5e672cca:JNLP4-connect connection to jenkins-agent/10.15.54.222:5": Remote call on JNLP4-connect connection to jenkins-agent/10.15.54.222:5 failed. The channel is closing down or has closed down at hudson.remoting.Channel.call(Channel.java:948) at hudson.remoting.Channel.syncIO(Channel.java:1683) at hudson.Launcher$RemoteLaunchCallable$1.join(Launcher.java:1331) 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:498) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:929) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:903) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:855) at hudson.remoting.UserRequest.perform(UserRequest.java:211) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:97)
[JIRA] (JENKINS-60953) Publish HTML report in Jenkins Pipeline Build
Title: Message Title Chandrakumar Sekar updated an issue Jenkins / JENKINS-60953 Publish HTML report in Jenkins Pipeline Build Change By: Chandrakumar Sekar Hello Team, I am facing an issue while publishing a HTML Report as part of my pipeline created. I am trying to publish a HTML report and once the report is published in Jenkins Job and respective build, the HTML report im trying to publish is being generated by Silk Performance Explorer and once it is generated im publishing it to the Jenkins using the Publish HMTL Report plugin, but once the pipeline is completed, the report is opening as blank, though the targeted main HTML page and its dependent objects are packed in the jobs folder of the jenkins in C drive. pls refer the attached view of the published report in jenkins build instance (Appears as white blank page). Could you please advise me on this issue? !image-2020-02-03-17-11-43-867.png! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message
[JIRA] (JENKINS-60953) Publish HTML report in Jenkins Pipeline Build
Title: Message Title Chandrakumar Sekar created an issue Jenkins / JENKINS-60953 Publish HTML report in Jenkins Pipeline Build Issue Type: Bug Assignee: Richard Bywater Attachments: image-2020-02-03-17-11-43-867.png Components: core, htmlpublisher-plugin Created: 2020-02-03 17:13 Environment: Jenkins 2.190, JDK 1.8, HTML publisher 1.21 Priority: Major Reporter: Chandrakumar Sekar Hello Team, I am facing an issue while publishing a HTML Report as part of my pipeline created. I am trying to publish a HTML report and once the report is published in Jenkins Job and respective build, the HTML report im trying to publish is being generated by Silk Performance Explorer and once it is generated im publishing it to the Jenkins using the Publish HMTL Report plugin, but once the pipeline is completed, the report is opening as blank, though the targeted main HTML page and its dependent objects are packed in the jobs folder of the jenkins in C drive. pls refer the attached view of the published report in jenkins build instance (Appears as white blank page).
[JIRA] (JENKINS-60264) Running a multibranch pipeline job results in missing workspace error
Title: Message Title
Daniel Estermann updated JENKINS-60264
I fixed it... it makes some sense now. The jenkins image I started within the test was using the same buildslave-configuration as the jenkins instance itself. It seems that it somehow affected the connections to the buildslaves, especially to the node where the test was running. I could workaround it like this:
script: """
mkdir /tmp/casc_configs/ && echo "" > /tmp/casc_configs/nodes.yaml && chown -R 1000:1000 /tmp/casc_configs/
docker run -e CASC_VAULT_TOKEN=${CASC_VAULT_TOKEN} \
--name jenkins \
-d \
-p 8080:8080 \
-v /tmp/casc_configs/:/var/jenkins_home/casc_configs/ \
${IMAGE_TAG}
mvn -Djenkins.test.timeout=${GLOBAL_TEST_TIMEOUT} -B -f Jenkins-Master/pom.xml test
"""
Jenkins / JENKINS-60264
Running a multibranch pipeline job results in missing workspace error
Change By:
Daniel Estermann
Status:
Open Fixed but Unreleased
Resolution:
Fixed
Add Comment
[JIRA] (JENKINS-60264) Running a multibranch pipeline job results in missing workspace error
Title: Message Title Daniel Estermann updated JENKINS-60264 Jenkins / JENKINS-60264 Running a multibranch pipeline job results in missing workspace error Change By: Daniel Estermann Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203252.1574679668000.150.1580749980674%40Atlassian.JIRA.
[JIRA] (JENKINS-60764) Allow configuration per folder rather than globally
Title: Message Title Chris Kilding edited a comment on JENKINS-60764 Re: Allow configuration per folder rather than globally Since your environments are deployed as separate AWS accounts, but you've got only one (environment-independent) Jenkins, it sounds like your intended setup is that Jenkins will run in a shared AWS tools account (not dev, QA, or prod).The options I can see are something like the following: # Put the secrets for each environment in the tooling account. Use the JEP-225 folder-based credentials ACL to restrict jobs so they can only access the right credentials. # Store the secrets in their respective environment accounts. We implement JENKINS-59670 (cross-account secret retrieval) so the plugin can fetch secrets from multiple accounts. * You give Jenkins IAM cross-account roles * to let so it can call Secrets Manager in those accounts *(this is far preferable to supplying 3 access key pairs)*. Then use the JEP-225 folder-based credentials ACL as in solution 1.Option 2 is considerably more work, and also increases the number of HTTP requests (and therefore lag, and the possibility for network failures) to list secrets.But in both cases, the JEP-225 credentials ACL should do what you're asking for. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204025.1579015116000
[JIRA] (JENKINS-44450) Block scoped usage
Title: Message Title Kalle Niemitalo commented on JENKINS-44450 Re: Block scoped usage Ulli Hafner, as the wiki is now read-only, do you accept comments on the requirements via some other channel? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182278.1495543785000.137.1580749080332%40Atlassian.JIRA.
[JIRA] (JENKINS-48955) master-slave connection getting terminated once in every 12 hours and recovered after 1 minute
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-48955 Re: master-slave connection getting terminated once in every 12 hours and recovered after 1 minute I usually request this info Common info needed to troubleshooting a bug to try to replicate the issue, but in this case, I guess that the 4th point would give you the solution directly when the issue happens should be an entry on the SSHD logs that said something that explains why the agent disconnect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187765.1516088319000.128.1580745840354%40Atlassian.JIRA.
[JIRA] (JENKINS-44085) have a simple way to limit the number of parallel branches that run concurrently
Title: Message Title Sam Gleske commented on JENKINS-44085 Re: have a simple way to limit the number of parallel branches that run concurrently No worries... in practice I haven't encountered the limitation I described. I still get the parallel speedup without completely taking over Jenkins infrastructure. So the limitation I posed is mostly hypothetical but may not actually impact your project. So it's at least worth trying out to see if you get any gains from it. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181710.1494001199000.81.1580745541379%40Atlassian.JIRA.
[JIRA] (JENKINS-60925) Integration with JIRA
Title: Message Title indu ch edited a comment on JENKINS-60925 Re: Integration with JIRA Thank you so much. It's working after creating API Token. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204322.158041457.78.1580745480417%40Atlassian.JIRA.
[JIRA] (JENKINS-60925) Integration with JIRA
Title: Message Title indu ch closed an issue as Incomplete Jenkins / JENKINS-60925 Integration with JIRA Change By: indu ch Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204322.158041457.74.1580745480360%40Atlassian.JIRA.
[JIRA] (JENKINS-60797) remote-file-plugin: enable selecting a fallback branch
Title: Message Title Aytunc BEKEN commented on JENKINS-60797 Re: remote-file-plugin: enable selecting a fallback branch You are welcome. I believe it too! I will start working on it and try to release as soon as possible. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204125.1579192122000.77.1580745480401%40Atlassian.JIRA.
[JIRA] (JENKINS-37929) WorkUnitContext.actions does not populate for Pipeline steps
Title: Message Title Jesse Glick resolved as Not A Defect Rurui Ye see above comments. Jenkins is behaving as designed. Jenkins / JENKINS-37929 WorkUnitContext.actions does not populate for Pipeline steps Change By: Jesse Glick Status: Reopened Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discus
[JIRA] (JENKINS-60897) JEP-225: Allow folders plugin to work with any credentials provider
Title: Message Title Chris Kilding updated an issue Jenkins / JENKINS-60897 JEP-225: Allow folders plugin to work with any credentials provider Change By: Chris Kilding Summary: JEP-225: Allow folders plugin to work with any credentials provider Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204287.158023331.69.1580744580179%40Atlassian.JIRA.
[JIRA] (JENKINS-60764) Allow configuration per folder rather than globally
Title: Message Title Chris Kilding commented on JENKINS-60764 Re: Allow configuration per folder rather than globally Since your environments are deployed as separate AWS accounts, but you've got only one (environment-independent) Jenkins, it sounds like your intended setup is that Jenkins will run in a shared AWS tools account (not dev, QA, or prod). The options I can see are something like the following: Put the secrets for each environment in the tooling account. Use the JEP-225 folder-based credentials ACL to restrict jobs so they can only access the right credentials. Store the secrets in their respective environment accounts. We implement JENKINS-59670 (cross-account secret retrieval) so the plugin can fetch secrets from multiple accounts. You give Jenkins IAM cross-account roles to let it call Secrets Manager in those accounts (this is far preferable to supplying 3 access key pairs). Then use the JEP-225 folder-based credentials ACL as in solution 1. Option 2 is considerably more work, and also increases the number of HTTP requests (and therefore lag, and the possibility for network failures) to list secrets. But in both cases, the JEP-225 credentials ACL should do what you're asking for. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and
[JIRA] (JENKINS-60925) Integration with JIRA
Title: Message Title indu ch commented on JENKINS-60925 Re: Integration with JIRA Thank you so much. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204322.158041457.65.1580744280559%40Atlassian.JIRA.
[JIRA] (JENKINS-59836) HashiCorp Vault plugin configuration cannot be enabled for Freestyle projects
Title: Message Title Marcus Brown commented on JENKINS-59836 Re: HashiCorp Vault plugin configuration cannot be enabled for Freestyle projects Agreed, seems to be working now. Thanks very much! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202571.1571380365000.51.1580743560468%40Atlassian.JIRA.
[JIRA] (JENKINS-60952) Update vulnerable dependencies in org.jenkins-ci.main:jenkins-core
Title: Message Title Adrian Wyssmann created an issue Jenkins / JENKINS-60952 Update vulnerable dependencies in org.jenkins-ci.main:jenkins-core Issue Type: Improvement Assignee: Unassigned Attachments: Violations_Export.json Components: core Created: 2020-02-03 15:24 Priority: Minor Reporter: Adrian Wyssmann [org.jenkins-ci.main:jenkins-core 2.204.2](https://mvnrepository.com/artifact/org.jenkins-ci.main/jenkins-core/2.204.2) appears to have several vulnerable dependencies. Are there any plans to update this? [INFO] +- org.jenkins-ci.main:jenkins-core:jar:2.204.2:compile [INFO] | +- org.jenkins-ci.plugins.icon-shim:icon-set:jar:1.0.5:compile [INFO] | +- org.jenkins-ci.main:remoting:jar:3.36.1:compile [INFO] | | - org.jenkins-ci:constant-pool-scanner:jar:1.2:compile [INFO] | +- org.jenkins-ci.main:cli:jar:2.204.2:compile [INFO] | | - net.i2p.crypto:eddsa:jar:0.3.0:compile [INFO] | +- org.jenkins-ci:version-number:jar:1.6:compile [INFO] | | - com.google.code.findbugs:annotations:jar:3.0.0:compile [INFO] | +- org.jenkins-ci:crypto-util:jar:1.1:compile [INFO] | +- org.jvnet.hudson:jtidy:jar:4aug2000r7-dev-hudson-1:compile [INFO] | +- com.google.inject:guice:jar:4.0:compile [INFO] | | +- javax.inject:javax.inject:jar:1:compile [INFO] | | - aopalliance:aopalliance:jar:1.0:compile [INFO] | +- org.connectbot.jbcrypt:jbcrypt:jar:1.0.0:compile [INFO] | +- org.jruby.ext.posix:jna-posix:jar:1.0.3-jenkins-1:compile [INFO] | +- com.github.jnr:jnr-posix:jar:3.0.45:compile [INFO] | | +- com.github.jnr:jnr-ffi:jar:2.1.8:compile [INFO] | | | +- com.github.jnr:jffi:jar:1.2.17:compile [
[JIRA] (JENKINS-60951) NPE Generic Webhook trigger plugin invoke
Title: Message Title Tomas Bjerre commented on JENKINS-60951 Re: NPE Generic Webhook trigger plugin invoke I interpret the stacktrace as if it is not a problem with Generic Webhook Trigger Plugin. Unassigning myself and removing the generic-webhook-trigger component. I also interpret it as a temporary problem that was solved with a reboot. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204410.1580741728000.47.1580742780121%40Atlassian.JIRA.
[JIRA] (JENKINS-60951) NPE Generic Webhook trigger plugin invoke
Title: Message Title Tomas Bjerre updated an issue Jenkins / JENKINS-60951 NPE Generic Webhook trigger plugin invoke Change By: Tomas Bjerre Component/s: generic-webhook-trigger-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204410.1580741728000.45.1580742720224%40Atlassian.JIRA.
[JIRA] (JENKINS-60951) NPE Generic Webhook trigger plugin invoke
Title: Message Title Tomas Bjerre assigned an issue to Unassigned Jenkins / JENKINS-60951 NPE Generic Webhook trigger plugin invoke Change By: Tomas Bjerre Assignee: Tomas Bjerre Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204410.1580741728000.43.1580742600670%40Atlassian.JIRA.
[JIRA] (JENKINS-60797) remote-file-plugin: enable selecting a fallback branch
Title: Message Title Tiran Meltser commented on JENKINS-60797 Re: remote-file-plugin: enable selecting a fallback branch Hi, Yes, I think a text field would be great (you can maybe also indicate in the description, that in case the desired branch doesn't exist, the mater branch would be used instead (same as today)). Thanks for going forward with this suggestion, I believe it would be very handy and make the plugin more robust. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204125.1579192122000.38.1580742240427%40Atlassian.JIRA.
[JIRA] (JENKINS-60951) NPE Generic Webhook trigger plugin invoke
Title: Message Title
Alexander Moiseenko updated an issue
Jenkins / JENKINS-60951
NPE Generic Webhook trigger plugin invoke
Change By:
Alexander Moiseenko
At some moment and until reboot all http requests like {{ [http://$|http://%24/]{JENKINS_URL}/generic-webhook-trigger/invoke?token=anything }} started to response with 500 error code and stacktrace:{noformat}java.lang.NullPointerException at org.jenkinsci.plugins.workflow.job.properties.PipelineTriggersJobProperty.getTriggersMap(PipelineTriggersJobProperty.java:133) at org.jenkinsci.plugins.workflow.job.WorkflowJob.getTriggers(WorkflowJob.java:425) at org.jenkinsci.plugins.gwt.jobfinder.JobFinder.findAllJobsWithTrigger(JobFinder.java:35) at org.jenkinsci.plugins.gwt.GenericWebHookRequestReceiver.doInvoke(GenericWebHookRequestReceiver.java:96) at org.jenkinsci.plugins.gwt.GenericWebHookRequestReceiver.doInvoke(GenericWebHookRequestReceiver.java:56) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747)Caused: javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:797) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$9.dispatch(MetaClass.java:456) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:873) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1623) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:246) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.auth.jwt.impl.JwtAuthenticationFilter.doFilter(JwtAuthenticationFilter.java:61) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:239) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:215) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:88) at org.jvnet.hudson.plugins.monitoring.HudsonMonitorin
[JIRA] (JENKINS-60951) NPE Generic Webhook trigger plugin invoke
Title: Message Title
Alexander Moiseenko created an issue
Jenkins / JENKINS-60951
NPE Generic Webhook trigger plugin invoke
Issue Type:
Bug
Assignee:
Tomas Bjerre
Components:
generic-webhook-trigger-plugin, workflow-job-plugin
Created:
2020-02-03 14:55
Environment:
Jenkins 2.176.3
Priority:
Minor
Reporter:
Alexander Moiseenko
At some moment and until reboot all http requests like {{http://$ {JENKINS_URL} /generic-webhook-trigger/invoke?token=anything}} started to response with 500 error code and stacktrace:
java.lang.NullPointerException
at org.jenkinsci.plugins.workflow.job.properties.PipelineTriggersJobProperty.getTriggersMap(PipelineTriggersJobProperty.java:133)
at org.jenkinsci.plugins.workflow.job.WorkflowJob.getTriggers(WorkflowJob.java:425)
at org.jenkinsci.plugins.gwt.jobfinder.JobFinder.findAllJobsWithTrigger(JobFinder.java:35)
at org.jenkinsci.plugins.gwt.GenericWebHookRequestReceiver.doInvoke(GenericWebHookRequestReceiver.java:96)
at org.jenkinsci.plugins.gwt.GenericWebHookRequestReceiver.doInvoke(GenericWebHookRequestReceiver.java:56)
at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627)
at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396)
at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212)
at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145)
at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)
at org.kohsuke.stap
[JIRA] (JENKINS-60797) remote-file-plugin: enable selecting a fallback branch
Title: Message Title Aytunc BEKEN commented on JENKINS-60797 Re: remote-file-plugin: enable selecting a fallback branch Hi, Thanks for the suggestion. I think this make sense, master may not be the fallback branch always. So, I think a text field for defining fallback branch will be enough, right ? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204125.1579192122000.11.1580741340516%40Atlassian.JIRA.
[JIRA] (JENKINS-60797) remote-file-plugin: enable selecting a fallback branch
Title: Message Title Aytunc BEKEN started work on JENKINS-60797 Change By: Aytunc BEKEN Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204125.1579192122000.14.1580741340603%40Atlassian.JIRA.
[JIRA] (JENKINS-60171) HTTP 422 uploading Android APK artifact
Title: Message Title
Terry Wallace edited a comment on JENKINS-60171
Re: HTTP 422 uploading Android APK artifact
Mez, I installed 1.81 and now get a more informational error. It seems to be complaining about the Platform. Which as far as I can see should be automatic depending on the file we upload. And these are definately .apk files. This would also explain why the iOS builds are working just fine. If you are setting a platform type in the background, how are you ascertaining the type ?Terry.SCRIPT STEPS:[Pipeline] withCredentialsMasking supported pattern matches of $APPCENTER_API_TOKEN[Pipeline] {[Pipeline] stepFile found matching pattern: build/client/Dingo_google_universal_enterprise.apkCreating an upload resource for app.Create upload resource for app successful.RESULT:io.jenkins.plugins.appcenter.AppCenterException: Upload app to resource unsuccessful: HTTP 422 Unprocessable Entity: {"status":"error","message":"Platform does not match. Expected value: iOS. Actual value: Android."} at io.jenkins.plugins.appcenter.AppCenterLogger.logFailure(AppCenterLogger.java:23) at io.jenkins.plugins.appcenter.AppCenterLogger.logFailure(AppCenterLogger.java:37) at io.jenkins.plugins.appcenter.task.internal.UploadAppToResourceTask.lambda$uploadApp$0(UploadAppToResourceTask.java:71)Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to BS MAC - VMAC-02 0872 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356) at hudson.remoting.Channel.call(Channel.java:955) at hudson.FilePath.act(FilePath.java:1159) at io.jenkins.plugins.appcenter.AppCenterRecorder.uploadToAppCenter(AppCenterRecorder.java:165) at io.jenkins.plugins.appcenter.AppCenterRecorder.perform(AppCenterRecorder.java:152) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266)Caused: java.util.concurrent.CompletionException at java.util.concurrent.CompletableFuture.encodeRelay(CompletableFuture.java:326) at java.util.concurrent.CompletableFuture.completeRelay(CompletableFuture.java:338) at java.util.concurrent.CompletableFuture.uniRelay(CompletableFuture.java:911) at java.util.concurrent.CompletableFuture$UniRelay.tryFire(CompletableFuture.java:899) at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474) at java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:1977) at io.jenkins.plugins.appcenter.task.internal.UploadAppToResourceTask.lambda$uploadApp$0(UploadAppToResourceTask.java:72) at java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:760) at java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:736) at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474) at java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:1977) at retrofit2.CompletableFutureCallAdapterFactory$BodyCallAdapter$2.onResponse(CompletableFutureCallAdapterFactory.java:81) at retrofit2.OkHttpCall$1.onResponse(OkHttpCall.java:129) at okhttp3.RealCall$AsyncCall.execute(RealCall.java:174) at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.co
[JIRA] (JENKINS-60171) HTTP 422 uploading Android APK artifact
Title: Message Title
Terry Wallace commented on JENKINS-60171
Re: HTTP 422 uploading Android APK artifact
Mez, I installed 1.81 and now get a more informational error. It seems to be complaining about the Platform. Which as far as I can see should be automatic depending on the file we upload. And these are definately .apk files. This would also explain why the iOS builds are working just fine. If you are setting a platform type in the background, how are you ascertaining the type ? Terry. SCRIPT STEPS: [Pipeline] withCredentials Masking supported pattern matches of $APPCENTER_API_TOKEN [Pipeline] { [Pipeline] step File found matching pattern: build/client/Dingo_google_universal_enterprise.apk Creating an upload resource for app. Create upload resource for app successful. RESULT: io.jenkins.plugins.appcenter.AppCenterException: Upload app to resource unsuccessful: HTTP 422 Unprocessable Entity: {"status":"error","message":"Platform does not match. Expected value: iOS. Actual value: Android."} at io.jenkins.plugins.appcenter.AppCenterLogger.logFailure(AppCenterLogger.java:23) at io.jenkins.plugins.appcenter.AppCenterLogger.logFailure(AppCenterLogger.java:37) at io.jenkins.plugins.appcenter.task.internal.UploadAppToResourceTask.lambda$uploadApp$0(UploadAppToResourceTask.java:71) Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to BS-VMAC-02 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356) at hudson.remoting.Channel.call(Channel.java:955) at hudson.FilePath.act(FilePath.java:1159) at io.jenkins.plugins.appcenter.AppCenterRecorder.uploadToAppCenter(AppCenterRecorder.java:165) at io.jenkins.plugins.appcenter.AppCenterRecorder.perform(AppCenterRecorder.java:152) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) Caused: java.util.concurrent.CompletionException at java.util.concurrent.CompletableFuture.encodeRelay(CompletableFuture.java:326) at java.util.concurrent.CompletableFuture.completeRelay(CompletableFuture.java:338) at java.util.concurrent.CompletableFuture.uniRelay(CompletableFuture.java:911) at java.util.concurrent.CompletableFuture$UniRelay.tryFire(CompletableFuture.java:899) at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474) at java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:1977) at io.jenkins.plugins.appcenter.task.internal.UploadAppToResourceTask.lambda$uploadApp$0(UploadAppToResourceTask.java:72) at java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:760) at java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:736) at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474) at java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:1977) at retrofit2.CompletableFutureCallAdapterFactory$BodyCallAdapter$2.onResponse(CompletableFutureCallAdapterFactory.java:81) at retrofit2.OkHttpCall$1.onResponse(OkHttpCall.java:129) at okhttp3.RealCall$AsyncCall.execute(RealCall.java:174) at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecut
[JIRA] (JENKINS-48625) Several git repo browser URL formats are not checked or documented
Title: Message Title Rishabh Budhouliya started work on JENKINS-48625 Change By: Rishabh Budhouliya Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187279.1513683224000.10815.1580736540428%40Atlassian.JIRA.
[JIRA] (JENKINS-60925) Integration with JIRA
Title: Message Title Radek Antoniuk resolved as Incomplete I mentioned the guide already above that is documented on Jira Cloud section of https://plugins.jenkins.io/jira - follow this https://developer.atlassian.com/cloud/jira/platform/basic-auth-for-rest-apis/ Jenkins / JENKINS-60925 Integration with JIRA Change By: Radek Antoniuk Status: Open Resolved Resolution: Incomplete Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop rece
[JIRA] (JENKINS-60925) Integration with JIRA
Title: Message Title indu ch commented on JENKINS-60925 Re: Integration with JIRA Thank you for your reply , dashboard means Jira cloud. Please guide me how can i create API token in Jira though we are using sso jira. I appreciate your time. Thanks, Rani Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204322.158041457.10811.1580736061379%40Atlassian.JIRA.
[JIRA] (JENKINS-48300) Pipeline shell step aborts prematurely with ERROR: script returned exit code -1
Title: Message Title Christopher Shannon commented on JENKINS-48300 Re: Pipeline shell step aborts prematurely with ERROR: script returned exit code -1 In case it helps anyone else who stumbles across this thread, I just ran into this problem and was able to figure out why (which was not a durable-step, or Jenkins thing, but something I was doing wrong). I basically had three different stages in my pipeline using static code analysis tools. Each of these tools can be CPU intensive and by default are happy to consume as many cores as are available on the host. We also have multiple Jenkins executors for each of our nodes (e.g. 4 executors on a 4 core node). This problem presented itself when I put these three stages in a parallel block, and they all mapped to three executors on the same physical node. When they started analyzing the code, I'm sure that my system load was completely railed (i.e. 2 if not 3 processes each trying to peg every core to 100% CPU). It is no surprise that this error message would occur in this scenario. Sure, Jenkins could have been more patient, but it also pointed to a pipeline architecture problem on my end. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186889.1511985014000.10809.1580735761448%40Atlassian.JIRA.
[JIRA] (JENKINS-60897) Allow folders plugin to work with any credentials provider
Title: Message Title Chris Kilding commented on JENKINS-60897 Re: Allow folders plugin to work with any credentials provider JENKINS-58951 is to implement JCasC support for the folders plugin. This might need to be implemented before we can add the ACL on top. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204287.158023331.10778.1580735640150%40Atlassian.JIRA.
[JIRA] (JENKINS-58951) Add YAML Configurator for folders in JCasC
Title: Message Title Chris Kilding commented on JENKINS-58951 Re: Add YAML Configurator for folders in JCasC This is potentially a prerequisite for JEP-225 (folders-based ACL for any credentials provider), as we'd like to specify the ACL declaratively in YAML, probably somewhere on the folders plugin config. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201298.1565877288000.10773.1580735520209%40Atlassian.JIRA.
[JIRA] (JENKINS-44411) Support throttling of blocks without node() in the throttle() step
Title: Message Title Simon K commented on JENKINS-44411 Re: Support throttling of blocks without node() in the throttle() step Hi, we switched to the lock-Plugin for this use case: https://wiki.jenkins.io/display/JENKINS/Lockable+Resources+Plugin Worked as aspected Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182237.1495446957000.10761.1580735460300%40Atlassian.JIRA.
[JIRA] (JENKINS-60950) ifferences between PreBuildMerge and MergeWithSCMExtention
Title: Message Title Loghi Perinpanayagam created an issue Jenkins / JENKINS-60950 ifferences between PreBuildMerge and MergeWithSCMExtention Issue Type: Improvement Assignee: Mark Waite Components: git-plugin Created: 2020-02-03 13:09 Priority: Minor Reporter: Loghi Perinpanayagam What are the differences between PreBuildMerge and MergeWithSCMExtention and how the race condition solves by using hash? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60950) Differences between PreBuildMerge and MergeWithSCMExtention
Title: Message Title Loghi Perinpanayagam updated an issue Jenkins / JENKINS-60950 Differences between PreBuildMerge and MergeWithSCMExtention Change By: Loghi Perinpanayagam Summary: ifferences Differences between PreBuildMerge and MergeWithSCMExtention Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204352.1580735353000.10759.1580735400372%40Atlassian.JIRA.
[JIRA] (JENKINS-48955) master-slave connection getting terminated once in every 12 hours and recovered after 1 minute
Title: Message Title Ian Katz commented on JENKINS-48955 Re: master-slave connection getting terminated once in every 12 hours and recovered after 1 minute I see that this has been closed as "can't reproduce". Assuming that you could reproduce the issue, what data would you record? I can try to do that and open a new issue with the requested data next time I experience this issue (which happens regularly) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187765.1516088319000.10750.1580735340490%40Atlassian.JIRA.
[JIRA] (JENKINS-60949) [EnvInject] Injecting properties of previous build breaks SCM polling
Title: Message Title Sebastian Ratz created an issue Jenkins / JENKINS-60949 [EnvInject] Injecting properties of previous build breaks SCM polling Issue Type: Bug Assignee: Unassigned Components: envinject-plugin Created: 2020-02-03 12:16 Priority: Major Reporter: Sebastian Ratz The EnvInject plugin re-injects the environment of the previous build into the SCM poll for the next build. However, it does this blindly, without considering when and where the previous build happened, and without knowing if the properties are actually applicable. Scenario: Have 2 slaves (slave-linux, slave-windows) Configure job for SCM polling Build job for the first time -> runs on slave-linux** builds/1/injectedEnvVars.txt contains, for example, HOME=/home/jenkins **Wait for next SCM poll. SCM poll runs on slave-windows this time. EnvInject blindly takes the env vars from injectedEnvVars.txt from build 1 and injects it into the SCM polling process. SCM polling on Windows fails, e.g. with "Could not create directory '/home/jenkins/.ssh'." because of the wrong HOME environment variable. Is there a way to prevent this? The job in question does not even make use of the EnvInject functionality, yet, injecting still happens at SCM polling time.
[JIRA] (JENKINS-28043) Reload configs of all jobs in folder
Title: Message Title Steve Graham edited a comment on JENKINS-28043 Re: Reload configs of all jobs in folder Just created a whole load of jobs in a Folder. Did a mass change inside the config files manually ( using a script ) Reloaded config ManageJenkins->reload configuration from discJenkins updated, jobs inside folders were not updated I'll go for the :( above...*Jenkins Version 2.219 *( tried it on an earlier version, thought I had done something wrong, only a few jobs so changed using Jenkins GUI .. and ignored it.)All latest plugins installed Raised it to Major I have many jobs in folders and changing e.g. the clearcase branch in 20+ jobs using the Jenkins GUI is not amusing when a perl one liner does it almost instantly. < /td> Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.162242.1429721391000.10732.1580732040403%40Atlassian.JIRA.
[JIRA] (JENKINS-28043) Reload configs of all jobs in folder
Title: Message Title Steve Graham edited a comment on JENKINS-28043 Re: Reload configs of all jobs in folder Just created a whole load of jobs in a Folder. Did a mass change inside the config files manually ( using a script ) Reloaded config ManageJenkins->reload configuration from discJenkins updated, jobs inside folders were not updated I'll go for the :( above...*Jenkins Version 2.219 *( tried it on an earlier version, thought I had done something wrong, only a few jobs so changed using Jenkins GUI .. and ignored it.) All latest plugins installed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.162242.1429721391000.10714.1580731563138%40Atlassian.JIRA.
[JIRA] (JENKINS-28043) Reload configs of all jobs in folder
Title: Message Title Steve Graham updated an issue Jenkins / JENKINS-28043 Reload configs of all jobs in folder Change By: Steve Graham Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.162242.1429721391000.10716.1580731563299%40Atlassian.JIRA.
[JIRA] (JENKINS-28043) Reload configs of all jobs in folder
Title: Message Title Steve Graham commented on JENKINS-28043 Re: Reload configs of all jobs in folder Just created a whole load of jobs in a Folder. Did a mass change inside the config files manually ( using a script ) Reloaded config ManageJenkins->reload configuration from disc Jenkins updated, jobs inside folders were not updated I'll go for the above... *Jenkins Version 2.219 * ( tried it on an earlier version, thought I had done something wrong, only a few jobs so changed using Jenkins GUI .. and ignored it.) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.162242.1429721391000.10684.1580731500515%40Atlassian.JIRA.
[JIRA] (JENKINS-60948) Branch indexing is ~5x -> 20x slower in v0.4.1 vs v0.3.3
Title: Message Title Luca Domenico Milanesio commented on JENKINS-60948 Re: Branch indexing is ~5x -> 20x slower in v0.4.1 vs v0.3.3 Johannes Carlsson thanks for reporting the issue. In a nutshell, the changes with 0.4.1 were composed of: Fetch of individual refs instead of refs/changes/* Use of the Checks API to filter out the changes that do not need validation With the combination of 1. and 2. the branch reindexing time would be a lot faster in 0.4.1 compared to 0.3.3. However, in your case, you do not have 2. because you are not using the Checks plugin. Also, by looking at your Gerrit httpd_log, it looks like the repository doesn't have a lot of refs and thus you do not see a benefit but, instead, a performance regression. When the repository has lots of refs (hundreds of thousands), fetching refs/changes/* (what the v0.3.3 was doing) may take tens of minutes and, in extreme cases, also up to 1h. That is why I changed the approach and did the fetch of the individual refs, which is slower in your case. Let me see if I can "convince" Jenkins that the subsequent "fetch" isn't needed and thus cut the tail of git-upload-pack after the query changes API. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an emai
