[JIRA] (JENKINS-52966) Two sequential stages in a parallel stage in a declarative pipeline making use of the same agent can cause a StackOverflowError
Title: Message Title Louis Heche commented on JENKINS-52966 Re: Two sequential stages in a parallel stage in a declarative pipeline making use of the same agent can cause a StackOverflowError Yes exactly we haven't done any update, this problem appear when we add some steps in our pipeline. We do have the following plugin installed pipeline model api 1.3.4 pipeline stage tags metadata 1.3.4 But we don't have the plugins pipeline model definition and pipeline model extensions installed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55050) Performance improvement for large archive symlink outside of workspace
Title: Message Title Wadeck Follonier started work on JENKINS-55050 Change By: Wadeck Follonier Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55594) NPE on not matching targets
Title: Message Title Aleksi Simell updated JENKINS-55594 Pull request merged. Jenkins / JENKINS-55594 NPE on not matching targets Change By: Aleksi Simell Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55638) cvs plugin broken - not possible to add new projects
Title: Message Title avinash reddy commented on JENKINS-55638 Re: cvs plugin broken - not possible to add new projects Hi Team, Could you please update me on this issue. it is blocking our work kindly provide the solution. Thanks, Avinash Aleti Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55640) java.lang.OutOfMemoryError: GC overhead limit exceeded
Title: Message Title
Daniel Issac created an issue
Jenkins / JENKINS-55640
java.lang.OutOfMemoryError: GC overhead limit exceeded
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
archived-artifact-url-viewer-plugin
Created:
2019-01-17 06:17
Environment:
Jenkins v2.138.2
Labels:
jenkins crash
Priority:
Major
Reporter:
Daniel Issac
Hi, We are seeing our CI jenkins server crashing frequently(atleast once in a day) with error: java.lang.OutOfMemoryError: GC overhead limit exceeded {{}} We collected Heap dump and tried to analyse using Eclipe Memory Analyser tool(Eclipse MAT).We see below message in the report: The thread java.lang.Thread @ 0x5d69c4500 Handling GET /job//descriptorByName/hudson.tasks.ArtifactArchiver/checkArtifacts from 10.158.222.25 : qtp1830908236-16408 keeps local variables with total size 1,949,995,728 (24.49%) bytes. what does this mean? In that job,we archive a file by proving variable name.How do we fix this issue? More info on Heap size used: Heap Configuration: MinHeapFreeRatio = 0 MaxHeapFreeRatio = 100 MaxHeapSize = 8589934592 (8192.0MB) NewSize = 2147483648 (2048.0MB) MaxNewSize = 2147483648 (2048.0MB) OldSize = 6442450944 (6144.0MB) NewRatio = 3 SurvivorRatio = 6 MetaspaceSize = 21807104 (20.796875MB) CompressedClassSpaceSize = 1073741824 (1024.0MB) MaxMetaspaceSize = 17592186044415 MB G1HeapRegionSize = 0 (0.0MB)
[JIRA] (JENKINS-55639) ec2-plugin only attempts to retrieve spot instance using old id
Title: Message Title
Tao Yang updated an issue
Jenkins / JENKINS-55639
ec2-plugin only attempts to retrieve spot instance using old id
Change By:
Tao Yang
When Jenkins attempts to provision spot instances, after spot requests are created (incorrectly, as per JENKINS-55618) Jenkins will try to retrieve the spot instance based on the last working instance id from before we upgraded the plugin was upgraded , instead of the instance id returned by the spot request. {code:java}INFO: Spot instance id in provision: sir-34si4rxjINFO: Spot instance id in provision: sir-34si4rxjJan 17, 2019 4:32:10 AM hudson.plugins.ec2.CloudHelper getInstanceINFO: Unexpected number of reservations reported by EC2 for instance id 'i-0b934d05d88272fc4', expected 1 result, found []. Instance seems to be dead.Jan 17, 2019 4:32:10 AM hudson.plugins.ec2.EC2Cloud provisionWARNING: SlaveTemplate{ami='ami-09009aeca3492b598', labels='agent linux'}. Exception during provisioningcom.amazonaws.AmazonClientException: Unexpected number of reservations reported by EC2 for instance id 'i-0b934d05d88272fc4', expected 1 result, found []. Instance seems to be dead. at hudson.plugins.ec2.CloudHelper.getInstance(CloudHelper.java:54) at hudson.plugins.ec2.CloudHelper.getInstanceWithRetry(CloudHelper.java:25) at hudson.plugins.ec2.EC2AbstractSlave.fetchLiveInstanceData(EC2AbstractSlave.java:499) at hudson.plugins.ec2.EC2AbstractSlave.(EC2AbstractSlave.java:159) at hudson.plugins.ec2.EC2SpotSlave.(EC2SpotSlave.java:44) at hudson.plugins.ec2.EC2SpotSlave.(EC2SpotSlave.java:37) at hudson.plugins.ec2.SlaveTemplate.newSpotSlave(SlaveTemplate.java:979) at hudson.plugins.ec2.SlaveTemplate.provisionSpot(SlaveTemplate.java:919) at hudson.plugins.ec2.SlaveTemplate.provision(SlaveTemplate.java:464) at hudson.plugins.ec2.EC2Cloud.getNewOrExistingAvailableSlave(EC2Cloud.java:578) at hudson.plugins.ec2.EC2Cloud.provision(EC2Cloud.java:594) at hudson.slaves.NodeProvisioner$StandardStrategyImpl.apply(NodeProvisioner.java:715) at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:320) at hudson.slaves.NodeProvisioner.access$000(NodeProvisioner.java:61) at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:809) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:72) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748){code}This hasn't happened with on-demand instances.This may be
[JIRA] (JENKINS-54656) cvs plugin broken - not possible to add new projects
Title: Message Title avinash reddy commented on JENKINS-54656 Re: cvs plugin broken - not possible to add new projects am also facing same issue. can any one provide the solution My Jenkin version is 2.150.1 CVS- Plugin version is 2.14 while saving new job am getting this error. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53735) Parallel sequential stages not showing Triggered Builds while Processing
Title: Message Title Olivier Lamy commented on JENKINS-53735 Re: Parallel sequential stages not showing Triggered Builds while Processing Elie Kassis sorry but no spare time ATM to work on it. Please remember blueocean is an opensource project so feel free to contribute. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53735) Parallel sequential stages not showing Triggered Builds while Processing
Title: Message Title Olivier Lamy assigned an issue to Unassigned Jenkins / JENKINS-53735 Parallel sequential stages not showing Triggered Builds while Processing Change By: Olivier Lamy Assignee: Olivier Lamy Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55639) ec2-plugin only attempts to retrieve spot instance using old id
Title: Message Title
Tao Yang created an issue
Jenkins / JENKINS-55639
ec2-plugin only attempts to retrieve spot instance using old id
Issue Type:
Bug
Assignee:
FABRIZIO MANFREDI
Components:
ec2-plugin
Created:
2019-01-17 05:20
Environment:
Jenkins 2.150.2 ec2-plugin 1.42
Priority:
Blocker
Reporter:
Tao Yang
When Jenkins attempts to provision spot instances, after spot requests are created (incorrectly, as per JENKINS-55618) Jenkins will try to retrieve the spot instance based on the last working instance id from before the plugin was upgraded, instead of the instance id returned by the spot request.
INFO: Spot instance id in provision: sir-34si4rxjINFO: Spot instance id in provision: sir-34si4rxjJan 17, 2019 4:32:10 AM hudson.plugins.ec2.CloudHelper getInstanceINFO: Unexpected number of reservations reported by EC2 for instance id 'i-0b934d05d88272fc4', expected 1 result, found []. Instance seems to be dead.Jan 17, 2019 4:32:10 AM hudson.plugins.ec2.EC2Cloud provisionWARNING: SlaveTemplate{ami='ami-09009aeca3492b598', labels='agent linux'}. Exception during provisioningcom.amazonaws.AmazonClientException: Unexpected number of reservations reported by EC2 for instance id 'i-0b934d05d88272fc4', expected 1 result, found []. Instance seems to be dead. at hudson.plugins.ec2.CloudHelper.getInstance(CloudHelper.java:54) at hudson.plugins.ec2.CloudHelper.getInstanceWithRetry(CloudHelper.java:25) at hudson.plugins.ec2.EC2AbstractSlave.fetchLiveInstanceData(EC2AbstractSlave.java:499) at hudson.plugins.ec2.EC2AbstractSlave.(EC2AbstractSlave.java:159) at
[JIRA] (JENKINS-55638) cvs plugin broken - not possible to add new projects
Title: Message Title avinash reddy created an issue Jenkins / JENKINS-55638 cvs plugin broken - not possible to add new projects Issue Type: Bug Assignee: Unassigned Components: cvs-plugin Created: 2019-01-17 05:14 Environment: Jenkins version 2.150.1 CVS plug-in version is 2.14 OS: windows 10 Priority: Blocker Reporter: avinash reddy The plugin crashes when trying to save a new project or edit an existing one (with a configured CVS repository). The problem seems to be the Exclude Regions setting, which does not show an input field and hence is null in the constructor. I will attach a screenshot of the settings dialog. The stack trace is this: java.lang.NullPointerExceptionjava.lang.NullPointerException at hudson.scm.CvsRepository.(CvsRepository.java:87) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at org.kohsuke.stapler.RequestImpl.invokeConstructor(RequestImpl.java:529) at org.kohsuke.stapler.RequestImpl.instantiate(RequestImpl.java:784) at org.kohsuke.stapler.RequestImpl.access$200(RequestImpl.java:83) at org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:678) at org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:717) at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:478) at org.kohsuke.stapler.RequestImpl.instantiate(RequestImpl.java:778) at org.kohsuke.stapler.RequestImpl.access$200(RequestImpl.java:83) at org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:678) at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:478) at
[JIRA] (JENKINS-54612) Reference repo not used for Git clones on Windows SSH agents
Title: Message Title dheeraj reddy commented on JENKINS-54612 Re: Reference repo not used for Git clones on Windows SSH agents I am also facing the exact issue(same environment also) while using git plugin (either as pipeline code or freestyle job). Using cmd or sh script I am able to clone it utilizing reference repo. May I know is there any bug on the git plugin ?? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55637) Error with Multibranch Pipeline
Title: Message Title Jie Shen commented on JENKINS-55637 Re: Error with Multibranch Pipeline back log Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55637) Error with Multibranch Pipeline
Title: Message Title
Jie Shen updated an issue
Jenkins / JENKINS-55637
Error with Multibranch Pipeline
Change By:
Jie Shen
Moved from github. geogeocutcut: When I use freestyle projet, the deployement run perfectly.When I use pipeline projet, it's ok. ` {code:java} [Pipeline] azureWebAppPublishStarting Azure Web App DeploymentCloning repository https://smag-testjenkins.scm.azurewebsites.net:443/smag-testjenkins.git > F:\Programs\Git\bin\git.exe init F:\workspace\Labs\Smag.gle.pipeline@2\.azure-deploy # timeout=10Fetching upstream changes from https://smag-testjenkins.scm.azurewebsites.net:443/smag-testjenkins.git > F:\Programs\Git\bin\git.exe --version # timeout=10using GIT_ASKPASS to set credentials > F:\Programs\Git\bin\git.exe fetch --tags --progress https://smag-testjenkins.scm.azurewebsites.net:443/smag-testjenkins.git +refs/heads/ * :refs/remotes/origin/ * > F:\Programs\Git\bin\git.exe config remote.origin.url https://smag-testjenkins.scm.azurewebsites.net:443/smag-testjenkins.git # timeout=10 > F:\Programs\Git\bin\git.exe config --add remote.origin.fetch +refs/heads/ * :refs/remotes/origin/ * # timeout=10Seen branch in repository origin/masterSeen 1 remote branch > F:\Programs\Git\bin\git.exe config core.sparsecheckout # timeout=10 > F:\Programs\Git\bin\git.exe checkout -f master > F:\Programs\Git\bin\git.exe add HelloWorld.sln # timeout=10 ...` {code} But when I use multibranch pipeline, I have an error ` {code:java} [Pipeline] azureWebAppPublish16:00:42 Starting Azure Web App Deployment16:00:44 Cloning repository https://smag-testjenkins.scm.azurewebsites.net:443/smag-testjenkins.git16:00:44 > F:\Programs\Git\bin\git.exe init F:\workspace\smag.gle\develop\.azure-deploy # timeout=1016:00:44 Fetching upstream changes from https://smag-testjenkins.scm.azurewebsites.net:443/smag-testjenkins.git16:00:44 > F:\Programs\Git\bin\git.exe --version # timeout=1016:00:44 using GIT_ASKPASS to set credentials 16:00:44 > F:\Programs\Git\bin\git.exe fetch --tags --progress https://smag-testjenkins.scm.azurewebsites.net:443/smag-testjenkins.git +refs/heads/ * :refs/remotes/origin/ * 16:01:04 > F:\Programs\Git\bin\git.exe config remote.origin.url https://smag-testjenkins.scm.azurewebsites.net:443/smag-testjenkins.git # timeout=1016:01:04 > F:\Programs\Git\bin\git.exe config --add remote.origin.fetch +refs/heads/ * :refs/remotes/origin/ * # timeout=1016:01:04 Seen branch in repository origin/master16:01:04 Seen 1 remote branch16:01:04 > F:\Programs\Git\bin\git.exe config core.sparsecheckout # timeout=1016:01:04 > F:\Programs\Git\bin\git.exe checkout -f master16:01:05 > F:\Programs\Git\bin\git.exe add F:/workspace/smag.gle/develop/HelloWorld.sln # timeout=10[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // ws[Pipeline] }[Pipeline] // node[Pipeline] }[Pipeline] // timestamps[Pipeline] End of Pipeline[Office365connector] No webhooks to notifyhudson.plugins.git.GitException: Command "F:\Programs\Git\bin\git.exe add F:/workspace/smag.gle/develop/HelloWorld.sln" returned status code
[JIRA] (JENKINS-55611) Make EXECUTOR_NUMBER available for yaml definition
Title: Message Title
Drum Big commented on JENKINS-55611
Re: Make EXECUTOR_NUMBER available for yaml definition
I'm talking about the environment variable "EXECUTOR_NUMBER" that jenkins defined (see https://wiki.jenkins.io/display/JENKINS/Building+a+software+project) Basically, we would like to assign the pod with a PVC with name "workspace-cache-${env.JOB_NAME}-${env.EXECUTOR_NUMBER}", this name will be unique across all concurrent build. But it is still reusable for builds that are not overlapping in theirs durations. Does that make sense?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55637) Error with Multibranch Pipeline
Title: Message Title Jie Shen created an issue Jenkins / JENKINS-55637 Error with Multibranch Pipeline Issue Type: Bug Assignee: Jie Shen Components: azure-app-service-plugin Created: 2019-01-17 03:02 Labels: github Priority: Minor Reporter: Jie Shen Moved from github. geogeocutcut: When I use freestyle projet, the deployement run perfectly. When I use pipeline projet, it's ok. `[Pipeline] azureWebAppPublish Starting Azure Web App Deployment Cloning repository https://smag-testjenkins.scm.azurewebsites.net:443/smag-testjenkins.git > F:\Programs\Git\bin\git.exe init F:\workspace\Labs\Smag.gle.pipeline@2\.azure-deploy # timeout=10 Fetching upstream changes from https://smag-testjenkins.scm.azurewebsites.net:443/smag-testjenkins.git > F:\Programs\Git\bin\git.exe --version # timeout=10 using GIT_ASKPASS to set credentials > F:\Programs\Git\bin\git.exe fetch --tags --progress https://smag-testjenkins.scm.azurewebsites.net:443/smag-testjenkins.git +refs/heads/:refs/remotes/origin/ > F:\Programs\Git\bin\git.exe config remote.origin.url https://smag-testjenkins.scm.azurewebsites.net:443/smag-testjenkins.git # timeout=10 > F:\Programs\Git\bin\git.exe config --add remote.origin.fetch +refs/heads/:refs/remotes/origin/ # timeout=10 Seen branch in repository origin/master Seen 1 remote branch > F:\Programs\Git\bin\git.exe config core.sparsecheckout # timeout=10 > F:\Programs\Git\bin\git.exe checkout -f master > F:\Programs\Git\bin\git.exe add HelloWorld.sln # timeout=10 ...` But when I use multibranch pipeline, I have an error `[Pipeline] azureWebAppPublish 16:00:42 Starting Azure Web App Deployment 16:00:44 Cloning repository https://smag-testjenkins.scm.azurewebsites.net:443/smag-testjenkins.git 16:00:44 > F:\Programs\Git\bin\git.exe init
[JIRA] (JENKINS-55636) Plugin doesn't use Jenkins proxy settings
Title: Message Title Jie Shen commented on JENKINS-55636 Re: Plugin doesn't use Jenkins proxy settings This should be a general feature across all the plugins. Need to investigate whether it is possible to implement it in the commons plugin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55636) Plugin doesn't use Jenkins proxy settings
Title: Message Title Jie Shen created an issue Jenkins / JENKINS-55636 Plugin doesn't use Jenkins proxy settings Issue Type: New Feature Assignee: Jie Shen Components: azure-app-service-plugin Created: 2019-01-17 02:59 Labels: github Priority: Minor Reporter: Jie Shen Moved from github. zentoaku: Hi, I've tried to setup the connection to Azure using this plugin on Jenkins behind corporate proxy but it seems like it doesn't use Jenkins proxy settings. Am I missing something? Error stack trace: java.net.UnknownHostException: login.microsoftonline.com at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:184) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:589) at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:673) at sun.security.ssl.BaseSSLSocketImpl.connect(BaseSSLSocketImpl.java:173) at sun.net.NetworkClient.doConnect(NetworkClient.java:180) at sun.net.www.http.HttpClient.openServer(HttpClient.java:463) at sun.net.www.http.HttpClient.openServer(HttpClient.java:558) at sun.net.www.protocol.https.HttpsClient.(HttpsClient.java:264) at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:367) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:191) at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1156) at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1050) at
[JIRA] (JENKINS-55635) Title for Windows Azure Storage Plugin
Title: Message Title Jie Shen commented on JENKINS-55635 Re: Title for Windows Azure Storage Plugin Changing a plugin's name is complex for Jenkins. Need more discussion here. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55635) Title for Windows Azure Storage Plugin
Title: Message Title Jie Shen created an issue Jenkins / JENKINS-55635 Title for Windows Azure Storage Plugin Issue Type: Task Assignee: Jie Shen Components: windows-azure-storage-plugin Created: 2019-01-17 02:46 Labels: github Priority: Minor Reporter: Jie Shen Moved from github. bbenz: Need to change the plugin description at https://plugins.jenkins.io/windows-azure-storage to Azure storage or Microsoft Azure Storage, currently it's Windows Azure Storage. Add Comment
[JIRA] (JENKINS-55633) Failing with Azure Stack
Title: Message Title Jie Shen commented on JENKINS-55633 Re: Failing with Azure Stack Low priority, back log. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55634) Specify credentials at runtime
Title: Message Title Jie Shen commented on JENKINS-55634 Re: Specify credentials at runtime back log Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55634) Specify credentials at runtime
Title: Message Title Jie Shen created an issue Jenkins / JENKINS-55634 Specify credentials at runtime Issue Type: Improvement Assignee: Jie Shen Components: windows-azure-storage-plugin Created: 2019-01-17 02:41 Labels: github Priority: Minor Reporter: Jie Shen Moved from github. shchukax: It would be useful to specify azure credentials at runtime. For example, in our build scenario, Azure credentials are loaded from a local file during the build. I cannot use jenkins credentials, as I don't know the account name/key before the pipeline runs. Add Comment
[JIRA] (JENKINS-55633) Failing with Azure Stack
Title: Message Title
Jie Shen updated an issue
Jenkins / JENKINS-55633
Failing with Azure Stack
Change By:
Jie Shen
Moved from github. charliejllewellyn: Hi I am trying to use this with Azure Stack. It is failing with:Hi I am trying to use this with Azure Stack. It is failing with: ``` {code:java} Failed to validate storage account details. Please verify storage account name and key. If you are using a private or other Windows Azure cloud service, make sure that the blob endpoint url is correct.Storage Account name -- - >jenkinsupload<-- -- Blob end point url --->https://jenkinsupload.blob.local.azurestack.external/<--- - ERROR: Step ‘Upload artifacts to Microsoft Azure Storage’ aborted due to exception: java.io.IOException: Plugin can not continue, until previous errors are addressed at com.microsoftopentechnologies.windowsazurestorage.WAStoragePublisher.perform(WAStoragePublisher.java:403) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:78) at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:32) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720) at hudson.model.Build$BuildExecution.post2(Build.java:186) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:665) at hudson.model.Run.execute(Run.java:1753) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:405) ``` {code} This could be for many reasons, SSL verification (although I have added the root cert to the java keystore), incorrect API versions, or incorrect resource provided in the token request. How can I enable debug logging and where should I look to troubleshoot this please. juniwang:Unfortunately we haven't tested the plugin in Azure Stack nor exposed the underlying exception. Might be better to verbose the underlying exception for debuging in next release.For now, it's really hard to find the root cause. But at my first sight, your blob endpoint Url https://jenkinsupload.blob.local.azurestack.external/ is beyond our expect. See https://github.com/jenkinsci/windows-azure-storage-plugin/blob/dev/src/main/java/com/microsoftopentechnologies/windowsazurestorage/helper/AzureUtils.java#L199. We tried to parse the endpoint suffix by finding substring `core` in the url. That means in your case, you didn't even try to connect to your AzureStack.If it's possible, could you please try to build and debug the plugin on your side? Sure we can do some fixes about logs/endpoints but it's hard for us to validate it since we don't have a AzureStack instance.
[JIRA] (JENKINS-55633) Failing with Azure Stack
Title: Message Title Jie Shen created an issue Jenkins / JENKINS-55633 Failing with Azure Stack Issue Type: Bug Assignee: Jie Shen Components: windows-azure-storage-plugin Created: 2019-01-17 02:36 Labels: github Priority: Minor Reporter: Jie Shen Moved from github. Hi I am trying to use this with Azure Stack. It is failing with:Hi I am trying to use this with Azure Stack. It is failing with: ```Failed to validate storage account details. Please verify storage account name and key. If you are using a private or other Windows Azure cloud service, make sure that the blob endpoint url is correct.Storage Account name -->jenkinsupload<--Blob end point url --->https://jenkinsupload.blob.local.azurestack.external/<---ERROR: Step ‘Upload artifacts to Microsoft Azure Storage’ aborted due to exception: java.io.IOException: Plugin can not continue, until previous errors are addressed at com.microsoftopentechnologies.windowsazurestorage.WAStoragePublisher.perform(WAStoragePublisher.java:403) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:78) at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:32) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720) at hudson.model.Build$BuildExecution.post2(Build.java:186) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:665) at hudson.model.Run.execute(Run.java:1753) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:405)``` This could be for many reasons, SSL verification (although I have added the root cert to the
[JIRA] (JENKINS-55613) OWASP Dependency Check Plugin hangs forever
Title: Message Title Steve Springett commented on JENKINS-55613 Re: OWASP Dependency Check Plugin hangs forever Please enable Jenkins logging for org.owasp and attach Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55613) OWASP Dependency Check Plugin hangs forever
Title: Message Title Steve Springett assigned an issue to Steve Springett Jenkins / JENKINS-55613 OWASP Dependency Check Plugin hangs forever Change By: Steve Springett Assignee: Steve Springett Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55632) Endless "Polling Dependency-Track for BoM processing status"
Title: Message Title Steve Springett resolved as Fixed This is already resolved and will be included in v2.1.0 of the plugin Jenkins / JENKINS-55632 Endless "Polling Dependency-Track for BoM processing status" Change By: Steve Springett Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55632) Endless "Polling Dependency-Track for BoM processing status"
Title: Message Title Mark Symons created an issue Jenkins / JENKINS-55632 Endless "Polling Dependency-Track for BoM processing status" Issue Type: Bug Assignee: Steve Springett Components: dependency-track-plugin Created: 2019-01-17 01:17 Environment: dependency-track-plugin v2.0.2 Jenkins v2.150.1 Dependency-Track Server v3.4.0 Priority: Major Reporter: Mark Symons During times when Dependency-Track server is experiencing maxed-out CPU usage, the dependency-track-plugin (operating in synchronous mode) will endlessly poll the DT server. The Jenkins job will continue running until it is aborted, logging the following to the console: [DependencyTrack] Publishing artifact to Dependency-Track [DependencyTrack] The artifact was successfully published [DependencyTrack] Polling Dependency-Track for BoM processing status [DependencyTrack] Polling Dependency-Track for BoM processing status ... The polling should have a timeout limit and then fail. This was originally reported as part of reporting high CPU usage in DT server (issue #264 and has been re-logged here in order to aid change control. Commits have already been made to address the defect. eg: Added polling timeout
[JIRA] (JENKINS-55527) Builds fail randomly when running sh in container
Title: Message Title Andy Powell commented on JENKINS-55527 Re: Builds fail randomly when running sh in container We are seeing similar errors. rpc error: code = 2 desc = oci runtime error: exec failed: container_linux.go:247: starting container process caused "process_linux.go:87: adding pid 3559144 to cgroups caused \"failed to write 3559144 to cgroup.procs: write /sys/fs/cgroup/cpu,cpuacct/kubepods/besteffort/pod03460050-19f2-11e9-beb6-42010a8e01b2/f4978b3f515bcf1f942bd0ed21ce084ca2039e6ae56f357870cbbe55517ed151/cgroup.procs: invalid argument\"" command terminated with non-zero exit code: Error executing in Docker Container: 126process apparently never started in /home/jenkins/workspace/le_platform-nodejs-hello_sandbox@tmp/durable-11cdeba1 Jenkins version = 2.150.1, running on GKE Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55631) docker.inside() cannot run container as privileged
Title: Message Title
Qijun Liu updated an issue
Jenkins / JENKINS-55631
docker.inside() cannot run container as privileged
Change By:
Qijun Liu
I tried to run a privileged Docker container with the Jenkins declarative pipeline (following this answer: [https://stackoverflow.com/questions/52409836/how-to-run-a-privileged-docker-container-with-the-jenkins-declarative-pipeline)] , by passing the "privileged" flag to the inside() function. The container is running but not in the privileged mode. Is there any way to make it work?My pipeline config is like this:stage('Test'){ steps { script { docker.image(DOCKER_REGISTRY + ":$BUILD_NUMBER").inside("--privileged -v /var/run/docker.sock:/var/run/docker.sock") { { sh '''. /usr/local/bin/test.sh''' } } } }
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55631) docker.inside() cannot run container as privileged
Title: Message Title
Qijun Liu created an issue
Jenkins / JENKINS-55631
docker.inside() cannot run container as privileged
Issue Type:
Bug
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2019-01-17 00:05
Priority:
Minor
Reporter:
Qijun Liu
I tried to run a privileged Docker container with the Jenkins declarative pipeline (following this answer: https://stackoverflow.com/questions/52409836/how-to-run-a-privileged-docker-container-with-the-jenkins-declarative-pipeline) The container is running but not in the privileged mode. Is there any way to make it work? My pipeline config is like this: stage('Test'){ steps { script { docker.image(DOCKER_REGISTRY + ":$BUILD_NUMBER").inside("--privileged -v /var/run/docker.sock:/var/run/docker.sock") { sh '''. /usr/local/bin/test.sh''' } } } }
Add Comment
[JIRA] (JENKINS-44609) Docker inspect failing on named multi-stage builds
Title: Message Title
Taylor Patton edited a comment on JENKINS-44609
Re: Docker inspect failing on named multi-stage builds
Also seeing this same issue, but interestingly enough, it works in 1 job but not another, doing almost the exact same thing.Working code in question:{code:java} withCredentials([string(credentialsId: 'secret-key', variable: 'secret')]) { docker.build('mydockerimage', "--file ${DOCKERFILE} --pull --build-arg KEY=${secret} --build-arg BUILD_NUMBER=${BUILD_NUMBER} .") } {code}Code that doesn't work:{code:java} withCredentials([string(credentialsId: 'secret-key', variable: 'secret')]) { docker.build('mydockerimage', "--file ${myProperties.DOCKERFILE} --pull --build-arg KEY=${secret} --build-arg BUILD_NUMBER=${params.BUILD_TO_DEPLOY} .") } {code}Where "myProperties" is read from a properties file using "readProperties" from stage utils plugin. The docker image seems to be built fine in both cases, but in the latter, we see the error:{code:java}Successfully built 204ce2321dabSuccessfully tagged [Pipeline] dockerFingerprintFrom[Pipeline] }[Pipeline] // withCredentials[Pipeline] }[Pipeline] // withDockerRegistry[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // node[Pipeline] End of Pipelinejava.io.IOException: Cannot retrieve .Id from 'docker inspect'{code}We do use the multi-stage docker build with "AS name" for the docker stages in the starting Dockerfile being built.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44609) Docker inspect failing on named multi-stage builds
Title: Message Title
Taylor Patton edited a comment on JENKINS-44609
Re: Docker inspect failing on named multi-stage builds
Also seeing this same issue, but interestingly enough, it works in 1 job but not another, doing almost the exact same thing.Working code in question:{code:java}withCredentials([string(credentialsId: 'secret-key', variable: 'secret')]) {docker.build('mydockerimage', "--file ${DOCKERFILE} --pull --build-arg KEY=${secret} --build-arg BUILD_NUMBER=${BUILD_NUMBER} .")} {code}Code that doesn't work:{code:java}withCredentials([string(credentialsId: 'secret-key', variable: 'secret')]) {docker.build('mydockerimage', "--file ${myProperties.DOCKERFILE} --pull --build-arg KEY=${secret} --build-arg BUILD_NUMBER=${ BUILD_NUMBER params.BUILD_TO_DEPLOY } .")} {code}Where "myProperties" is read from a properties file using "readProperties" from stage utils plugin. The docker image seems to be built fine in both cases, but in the latter, we see the error:{code:java}Successfully built 204ce2321dabSuccessfully tagged [Pipeline] dockerFingerprintFrom[Pipeline] }[Pipeline] // withCredentials[Pipeline] }[Pipeline] // withDockerRegistry[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // node[Pipeline] End of Pipelinejava.io.IOException: Cannot retrieve .Id from 'docker inspect'{code}We do use the multi-stage docker build with "AS name" for the docker stages in the starting Dockerfile being built.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55257) Timestamper break builds on Windows agents
Title: Message Title Jeff Thompson commented on JENKINS-55257 Re: Timestamper break builds on Windows agents If it's not connected with Remoting, my interest in reproducing it wanes. I'm satisfied that you have a handle on the cause and resolution. Unless you need me to review and test the PR. Of course, it would be better if someone who is actually experiencing the problem could do that. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44609) Docker inspect failing on named multi-stage builds
Title: Message Title
Taylor Patton commented on JENKINS-44609
Re: Docker inspect failing on named multi-stage builds
Also seeing this same issue, but interestingly enough, it works in 1 job but not another, doing almost the exact same thing. Working code in question:
withCredentials([string(credentialsId: 'secret-key', variable: 'secret')]) {
docker.build('mydockerimage', "--file ${DOCKERFILE} --pull --build-arg KEY=${secret} --build-arg BUILD_NUMBER=${BUILD_NUMBER} .")
}
Code that doesn't work:
withCredentials([string(credentialsId: 'secret-key', variable: 'secret')]) {
docker.build('mydockerimage', "--file ${myProperties.DOCKERFILE} --pull --build-arg KEY=${secret} --build-arg BUILD_NUMBER=${BUILD_NUMBER} .")
}
Where "myProperties" is read from a properties file using "readProperties" from stage utils plugin. The docker image seems to be built fine in both cases, but in the latter, we see the error:
Successfully built 204ce2321dab
Successfully tagged
[Pipeline] dockerFingerprintFrom
[Pipeline] }
[Pipeline] // withCredentials
[Pipeline] }
[Pipeline] // withDockerRegistry
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
java.io.IOException: Cannot retrieve .Id from 'docker inspect'
We do use the multi-stage docker build with "AS name" for the docker stages in the starting Dockerfile being built.
Add Comment
[JIRA] (JENKINS-55257) Timestamper break builds on Windows agents
Title: Message Title Jesse Glick commented on JENKINS-55257 Re: Timestamper break builds on Windows agents Oh, and probable way to reproduce (Jeff Thompson you might manage it): run an agent using an old version of slave.jar; use timestamper (without my fix); and run some step which produces remote logging, like git, or just sh if you are running with -Dorg.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep.USE_WATCHING=true. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55257) Timestamper break builds on Windows agents
Title: Message Title Jesse Glick updated JENKINS-55257 Jenkins / JENKINS-55257 Timestamper break builds on Windows agents Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55257) Timestamper break builds on Windows agents
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-55257 Timestamper break builds on Windows agents Change By: Jesse Glick Labels: remoting Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55257) Timestamper break builds on Windows agents
Title: Message Title Jesse Glick started work on JENKINS-55257 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55257) Timestamper break builds on Windows agents
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-55257 Timestamper break builds on Windows agents Change By: Jesse Glick Assignee: Jeff Thompson Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55257) Timestamper break builds on Windows agents
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-55257 Timestamper break builds on Windows agents Change By: Jesse Glick Component/s: core Component/s: remoting Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55257) Timestamper break builds on Windows agents
Title: Message Title Jesse Glick commented on JENKINS-55257 Re: Timestamper break builds on Windows agents In the meantime, I suspect core PR 3851 would fix the exception, if anyone wants to test it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55556) EC2 unable to retrieve private IP (+ other buggy behaviour)
Title: Message Title Shaun Lawrie edited a comment on JENKINS-6 Re: EC2 unable to retrieve private IP (+ other buggy behaviour) I have the same symptoms with spot instance private IP's not being identified by the ec2-plugin but ours also have public IP's assigned in the configuration.I downgraded to 1.39 so it behaves in the meantime. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55556) EC2 unable to retrieve private IP (+ other buggy behaviour)
Title: Message Title Shaun Lawrie commented on JENKINS-6 Re: EC2 unable to retrieve private IP (+ other buggy behaviour) I have the same symptoms with spot instance private IP's not being identified by the ec2-plugin but ours also have public IP's assigned in the configuration. I downgraded to 1.39 so it behaves in the meantime. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55257) Timestamper break builds on Windows agents
Title: Message Title Jesse Glick commented on JENKINS-55257 Re: Timestamper break builds on Windows agents That would be consistent with an older slave.jar that predates the addition of the org/jenkinsci/remoting/util/AnonymousClassWarnings.class entry. That in itself is unsurprising. The question is where the reference to this class comes from. Presumably it is being remotely loaded from the master, via ConsoleNote.encodeToBytes. I think the problem is that this method is being called from the agent side, which it should not. And that in turn means that the problem is solved by JENKINS-48344. So now we just need for Steven G Brown to merge my PR. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-1774) wrap long project names
Title: Message Title Alex Earl closed an issue as Incomplete No response to question after 3 years Jenkins / JENKINS-1774 wrap long project names Change By: Alex Earl Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46394) active choices reactive parameter cant load shared library
Title: Message Title Robert Grądzki commented on JENKINS-46394 Re: active choices reactive parameter cant load shared library I can help with the resting. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46394) active choices reactive parameter cant load shared library
Title: Message Title Robert Grądzki edited a comment on JENKINS-46394 Re: active choices reactive parameter cant load shared library I can help with the resting testing . Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-687) investigate graphical console
Title: Message Title Alex Earl closed an issue as Incomplete Please reopen with more information if you are still interested. Jenkins / JENKINS-687 investigate graphical console Change By: Alex Earl Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-510) Graph build size trends
Title: Message Title Alex Earl updated JENKINS-510 Jenkins / JENKINS-510 Graph build size trends Change By: Alex Earl Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-510) Graph build size trends
Title: Message Title Alex Earl updated JENKINS-510 This sounds like the disk usage plugin does this Jenkins / JENKINS-510 Graph build size trends Change By: Alex Earl Status: Reopened Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52397) Org Scan blows up when repository has no tags
Title: Message Title Karl Shultz commented on JENKINS-52397 Re: Org Scan blows up when repository has no tags rsandell - does the inclusion of this PR in 2.4.2 mean this bug has been fixed, and the ticket can be closed? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55139) ansicolor 0.6.0 shows terminal escape sequences in console log
Title: Message Title Devin Nusbaum commented on JENKINS-55139 Re: ansicolor 0.6.0 shows terminal escape sequences in console log Victor Verbitsky Maven coloring is explicitly validated in this test case. Are you sure that you are seeing that output for a build while you are still running Ansicolor 0.6.0? If you have Ansicolor 0.5.3 installed, then the logs are expected to look like that for builds that originally ran while Ansicolor 0.6.0 was installed. I am not able to reproduce your issue on Ansicolor 0.6.0. If you are able to create a similar test case to the Maven one I linked that demonstrates the issue you are seeing, that would be very helpful. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46394) active choices reactive parameter cant load shared library
Title: Message Title Bruno P. Kinoshita commented on JENKINS-46394 Re: active choices reactive parameter cant load shared library Looks like this is something useful for users. Next development cycle will start looking into ways other plugins are using to support that. I really want to avoid the plugin being blacklisted again due to security issues/CVE's. So my plain is 1. learn how other plugins are working 2. create a branch with the solution 3. upload here a .hpi file with the proposed solution, and also try to release to the experimental update site (not sure if that still exists) 4. release only, and really only, if there's enough testing from users that also took into consideration possible attack vectors created by this feature (i.e. giving some thought to what issues this feature could cause... do they have a security permission model that could allow users to use dangerous libraries? did we implement in a way that the administrator him/herself could shoot his own foot and accidentally introduce a security problem in their jenkins/etc) And once we pass step 4, and we are confident this won't introduce a security bug, cut a release. Let me know if anyone has any other suggestions, or if interested in helping with the testing/development. Cheers Bruno Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55630) Support declarative pipelines
Title: Message Title
Benjamin Muschko updated an issue
Jenkins / JENKINS-55630
Support declarative pipelines
Change By:
Benjamin Muschko
Currently, it only seems to be possible to create a scripted pipeline for Go projects with this plugin. I was struggling to find equivalent support for modeling a declarative pipeline. The issue I ran into: # Accessing a tool in a declarative pipeline should work just fine. # Defining a custom workspace is not allowed in a declarative pipeline. # Setting the environment variables for different build stages is impractical. If possible those environment variables should already be preset. This is how I solved the issue right now, however, Jenkins seems to move away from scripted pipelines toward declarative ones. Let me know if this is already possible. < { code > } node {def goHome = tool('go-1.11')ws("${JENKINS_HOME}/jobs/${JOB_NAME}/builds/${BUILD_ID}/src/github.com/bmuschko/link-verifier") {withEnv(["GOROOT=${goHome}", "GOPATH=${JENKINS_HOME}/jobs/${JOB_NAME}/builds/${BUILD_ID}/", "PATH+GO=${goHome}/bin"]) {...}} { code > }
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-55630) Support declarative pipelines
Title: Message Title
Benjamin Muschko updated an issue
Jenkins / JENKINS-55630
Support declarative pipelines
Change By:
Benjamin Muschko
Currently, it only seems to be possible to create a scripted pipeline for Go projects with this plugin. I was struggling to find equivalent support for modeling a declarative pipeline. The issue issues I ran into: # Accessing a tool in a declarative pipeline should work just fine. # Defining a custom workspace is not allowed in a declarative pipeline. # Setting the environment variables for different build stages is impractical. If possible those environment variables should already be preset. This is how I solved the issue right now, however, Jenkins seems to move away from scripted pipelines toward declarative ones. Let me know if this is already possible.{code}node {def goHome = tool('go-1.11')ws("${JENKINS_HOME}/jobs/${JOB_NAME}/builds/${BUILD_ID}/src/github.com/bmuschko/link-verifier") {withEnv(["GOROOT=${goHome}", "GOPATH=${JENKINS_HOME}/jobs/${JOB_NAME}/builds/${BUILD_ID}/", "PATH+GO=${goHome}/bin"]) {...}}{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-55630) Support declarative pipelines
Title: Message Title
Benjamin Muschko updated an issue
Jenkins / JENKINS-55630
Support declarative pipelines
Change By:
Benjamin Muschko
Currently, it only seems to be possible to create a scripted pipeline for Go projects with this plugin. I was struggling to find equivalent support for modeling a declarative pipeline. The issue I ran into: # Accessing a tool in a declarative pipeline should work just fine. # Defining a custom workspace is not allowed in a declarative pipeline. # Setting the environment variables for different build stages is impractical. If possible those environment variables should already be preset. This is how I solved the issue right now, however, Jenkins seems to move away from scripted pipelines toward declarative ones. Let me know if this is already possible. {{ node { }} {{ def goHome = tool('go-1.11') }} {{ ws("${JENKINS_HOME}/jobs/${JOB_NAME}/builds/${BUILD_ID}/src/github.com/bmuschko/link-verifier") { }} {{ withEnv(["GOROOT=${goHome}", "GOPATH=${JENKINS_HOME}/jobs/${JOB_NAME}/builds/${BUILD_ID}/", "PATH+GO=${goHome}/bin"]) { }} {{ ... }} {{ } }} {{ } }}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an
[JIRA] (JENKINS-55630) Support declarative pipelines
Title: Message Title
Benjamin Muschko created an issue
Jenkins / JENKINS-55630
Support declarative pipelines
Issue Type:
Improvement
Assignee:
Christopher Orr
Components:
golang-plugin
Created:
2019-01-16 21:31
Priority:
Major
Reporter:
Benjamin Muschko
Currently, it only seems to be possible to create a scripted pipeline for Go projects with this plugin. I was struggling to find equivalent support for modeling a declarative pipeline. The issue I ran into:
Accessing a tool in a declarative pipeline should work just fine.
Defining a custom workspace is not allowed in a declarative pipeline.
Setting the environment variables for different build stages is impractical. If possible those environment variables should already be preset.
This is how I solved the issue right now, however, Jenkins seems to move away from scripted pipelines toward declarative ones. Let me know if this is already possible. node { {{ def goHome = tool('go-1.11')}} {{ ws("${JENKINS_HOME}/jobs/${JOB_NAME}/builds/${BUILD_ID}/src/github.com/bmuschko/link-verifier") {}} withEnv(["GOROOT=${goHome}", "GOPATH=${JENKINS_HOME}/jobs/${JOB_NAME}/builds/${BUILD_ID}/", "PATH+GO=${goHome}/bin"]) { ... {{ }}} }
[JIRA] (JENKINS-55621) how can logstash plugin send multiple line once time to es with block usage?
Title: Message Title Markus Winter commented on JENKINS-55621 Re: how can logstash plugin send multiple line once time to es with block usage? This is not possible currently. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title Marky Jackson commented on JENKINS-55392 Re: java.util.concurrent.RejectedExecutionException AGAIN I’m syncing with the plugin maintainer in an effort to ensure what I think is the root cause is mutual and the best way forward. Given this plugin has wide adoption, it is always best to ensure there is a uniformed approach Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55612) Add optional label attribute for echo step to improve usability
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-55612 Add optional label attribute for echo step to improve usability Change By: Devin Nusbaum Labels: pipeline Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55612) Add optional label attribute for echo step to improve usability
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-55612 Add optional label attribute for echo step to improve usability Change By: Devin Nusbaum Component/s: workflow-basic-steps-plugin Component/s: pipeline Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title Daniel Watrous commented on JENKINS-55392 Re: java.util.concurrent.RejectedExecutionException AGAIN Marky Jackson I'm happy to help track this down, if you give me some pointers on how and where to look. Let me know if I can be helpful on this issue. I'm just not really sure where to start. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55624) Authorize Projects plugin causes no git credentials to be found with 'Run as Specific User' Strategy is set
Title: Message Title ikedam assigned an issue to Unassigned That looks caused for the newly added user doesn’t have a permission to access that credentials. It sounds an expected behavior. Anyway, this is an issue of credentials-plugin and I update the cemponent and the assignee. Jenkins / JENKINS-55624 Authorize Projects plugin causes no git credentials to be found with 'Run as Specific User' Strategy is set Change By: ikedam Component/s: credentials-plugin Component/s: authorize-project-plugin Assignee: ikedam Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send
[JIRA] (JENKINS-55586) Credentials-binding plugin still masking deleted credentials in log
Title: Message Title p cowlinator commented on JENKINS-55586 Re: Credentials-binding plugin still masking deleted credentials in log Jasmine Jack, you seem to have included a link to an unrelated site. Did you mean to paste something else? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55368) No issues found when parsing Eclipse ECJ output from console log during maven build
Title: Message Title Piotrek Zygielo commented on JENKINS-55368 Re: No issues found when parsing Eclipse ECJ output from console log during maven build After upgrading plugin analysis-model-api to new release (2.0.1): report Eclipse ECJ Warnings is successfully created, with warnings collected from console violations in column File are correctly linked to descriptions Perfect. Thank you. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55629) Bitbucket source missing after upgrade to 2.4.0
Title: Message Title Vijay K updated an issue Jenkins / JENKINS-55629 Bitbucket source missing after upgrade to 2.4.0 Change By: Vijay K Jenkins Version: 2.7.4Bitbucket Branch Source Plugin Version: 2.4.0Bitbucket Branch Source Plugin previous Version: 1.8 Missing Option: "Bitbucket" in "Multibranch Pipeline -> Branch Sources" Doesn't give me an option to specify Repository. Couldn't proceed any further. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55368) No issues found when parsing Eclipse ECJ output from console log during maven build
Title: Message Title Piotrek Zygielo commented on JENKINS-55368 Re: No issues found when parsing Eclipse ECJ output from console log during maven build Hopefully fixed by commit#880efaa. I will verify ASAP. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55368) No issues found when parsing Eclipse ECJ output from console log during maven build
Title: Message Title Piotrek Zygielo commented on JENKINS-55368 Re: No issues found when parsing Eclipse ECJ output from console log during maven build If you are compiling with ErrorProne then you need to use the ErrorProne parser. I have separate jobs, for EP I'm of course using I refered to EP only as for working example. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55629) Bitbucket source missing after upgrade to 2.4.0
Title: Message Title Vijay K updated an issue Jenkins / JENKINS-55629 Bitbucket source missing after upgrade to 2.4.0 Change By: Vijay K Attachment: missing-Source.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54054) Job URL passed to webhook is incorrect (null base url) for manually triggered builds without SCM
Title: Message Title Jo Vandeginste closed an issue as Fixed Jenkins / JENKINS-54054 Job URL passed to webhook is incorrect (null base url) for manually triggered builds without SCM Change By: Jo Vandeginste Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55368) No issues found when parsing Eclipse ECJ output from console log during maven build
Title: Message Title Ulli Hafner commented on JENKINS-55368 Re: No issues found when parsing Eclipse ECJ output from console log during maven build Hopefully fixed by commit#880efaa. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55368) No issues found when parsing Eclipse ECJ output from console log during maven build
Title: Message Title Ulli Hafner commented on JENKINS-55368 Re: No issues found when parsing Eclipse ECJ output from console log during maven build If you are compiling with ErrorProne then you need to use the ErrorProne parser. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55629) Bitbucket source missing after upgrade to 2.4.0
Title: Message Title Vijay K created an issue Jenkins / JENKINS-55629 Bitbucket source missing after upgrade to 2.4.0 Issue Type: Bug Assignee: Unassigned Components: bitbucket-branch-source-plugin Created: 2019-01-16 19:23 Labels: plugin jenkins Priority: Blocker Reporter: Vijay K Jenkins Version: 2.7.4 Bitbucket Branch Source Plugin Version: 2.4.0 Bitbucket Branch Source Plugin previous Version: 1.8 Missing Option: "Bitbucket" in "Multibranch Pipeline -> Branch Sources" Couldn't proceed any further. Add Comment
[JIRA] (JENKINS-55368) No issues found when parsing Eclipse ECJ output from console log during maven build
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-55368 No issues found when parsing Eclipse ECJ output from console log during maven build Change By: Ulli Hafner Released As: warnings-ng 2.0.0, analysis-model-api 2.0. 0 1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55539) determining blame via git fails with out-off-tree builds
Title: Message Title Ulli Hafner commented on JENKINS-55539 Re: determining blame via git fails with out-off-tree builds Martin Karing: this is a different issue. BTW: if your files are not in the workspace it would be a high security risk to copy them so they are ignored. The same is true for git access. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55628) In Jenkins, Do we have any functionality similar to 'Finish build trigger of TeamCity
Title: Message Title Raj G created an issue Jenkins / JENKINS-55628 In Jenkins, Do we have any functionality similar to 'Finish build trigger of TeamCity Issue Type: Bug Assignee: Craig Rodrigues Components: build-flow-plugin Created: 2019-01-16 19:03 Priority: Minor Reporter: Raj G In Jenkins 2.138.2, Do we have any functionality similar to 'Finish build trigger of TeamCity ? This functionality in TeamCity will let you configure a pre-build task which will first run the target build and runs the current build job only if the target build is successful Add Comment
[JIRA] (JENKINS-55257) Timestamper break builds on Windows agents
Title: Message Title D Pasto commented on JENKINS-55257 Re: Timestamper break builds on Windows agents Does this mean anything? Result: [file:/C:/Jenkins/slave.jar, null] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55626) Build hangs using inheritFrom without a label
Title: Message Title Steve Boardwell updated an issue Jenkins / JENKINS-55626 Build hangs using inheritFrom without a label Change By: Steve Boardwell Component/s: kubernetes-ci-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55626) Build hangs using inheritFrom without a label
Title: Message Title
Steve Boardwell updated an issue
Jenkins / JENKINS-55626
Build hangs using inheritFrom without a label
Change By:
Steve Boardwell
h3. Problem StatementThe build hangs when using {{inheritFrom}} in a declarative pipeline (have not tested in a script pipeline) and you either * set an identical {{label}} to the one defined in the Pod Template* omit the {{label}} tag meaning the inherited label is used (i . e. almost identical) The problem is , however, that there is no information that something is wrong. The build just hangs. h3. To ReproduceUse the following (uncomment label to make it work):{noformat}pipeline {agent {kubernetes {inheritFrom 'nodejs'// THIS WOULD FAIL --> label ' jenkins-nodejs'// THIS WOULD BE OK --> label ' my-agent'containerTemplate {name 'nodejs'image 'jenkinsxio/builder-nodejs8x:0.1.187'}defaultContainer 'nodejs'}}stages {stage('Npm Check') {steps {sh 'npm -v'}}}post {always {cleanWs()}}}{noformat}From the Jenkins log:{noformat}Jan 16, 2019 5:01:51 PM org.jenkinsci.plugins.jx.resources.BuildSyncRunListener upsertBuildINFO: Updated pipeline activity .Jan 16, 2019 5:01:53 PM com.elasticbox.jenkins.k8s.services.task.ScheduledPoolingTask executeINFO: Pooling task: WaitForThePodToBeRunningTask finished successfullyJan 16, 2019 5:01:53 PM com.elasticbox.jenkins.k8s.services.slavesprovisioning.chain.steps.WaitForPodToBeRunning handleINFO: Pod is up and runningJan 16, 2019 5:01:59 PM com.elasticbox.jenkins.k8s.plugin.clouds.KubernetesCloud canProvisionINFO: Checking label: jenkins-jx-base.Jan 16, 2019 5:02:00 PM com.elasticbox.jenkins.k8s.plugin.clouds.KubernetesCloud canProvisionINFO: Checking label: jenkins-swiftJan 16, 2019 5:02:00 PM com.squareup.okhttp.internal.Platform$JdkWithJettyBootPlatform getSelectedProtocolINFO: ALPN callback dropped: SPDY and HTTP/2 are disabled. Is alpn-boot on the boot class path?Jan 16, 2019 5:02:53 PM com.elasticbox.jenkins.k8s.services.task.ScheduledPoolingTask executeSEVERE: Timeout reached(60 secs) executing task: WaitForTheSlaveToBeOnlineTaskJan 16, 2019 5:02:53 PM com.elasticbox.jenkins.k8s.services.slavesprovisioning.chain.steps.WaitForSlaveToBeOnline handleSEVERE: Error waiting for the Jenkins slave to be onlineJan 16, 2019 5:02:53 PM com.elasticbox.jenkins.k8s.services.SlaveProvisioningServiceImpl slaveProvisionSEVERE: Error provisioning Pod Jenkins slaveJan 16, 2019 5:02:57 PM hudson.slaves.NodeProvisioner$2 runWARNING: Unexpected exception encountered while provisioning agent Jenkins Kubernetes Slavecom.elasticbox.jenkins.k8s.services.error.ServiceException: Error waiting for the Jenkins slave to be online at com.elasticbox.jenkins.k8s.services.slavesprovisioning.chain.steps.WaitForSlaveToBeOnline.handle(WaitForSlaveToBeOnline.java:64) at
[JIRA] (JENKINS-55448) File cleaning failure, old build and plugin update
Title: Message Title Daniel Beck updated JENKINS-55448 Fixed in 2.159. Jenkins / JENKINS-55448 File cleaning failure, old build and plugin update Change By: Daniel Beck Status: In Review Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51965) Add support of JAXB unpackaging for Java 9+ in WAR Exploder
Title: Message Title Baptiste Mathus commented on JENKINS-51965 Re: Add support of JAXB unpackaging for Java 9+ in WAR Exploder A new update: after Oleg recommended I try the SlocCount plugin, I did. And it does fail as expected on Java 11 by default. I filed JENKINS-55620 to track this. So then I tried dropping directly jaxb-api-2.3.0.jar and jaxb-core-2.3.0.1.jar into various locations to see how it behaves. Everything worked fine. Java 8 Java 11 Plugin's WEB-INF/lib OK OK Jenkins' war/WEB-INF/lib OK OK To summarize, it seems like hardcoding the dependency against JAXB directly in the plugin would be simpler. I'm not saying it will work in every single case, where/if a given plugin does something more convoluted, trying for instance to use JAXB instances coming from another plugin (which I think, but untested yet, would result in having the classes seen as different given classloaders would be different). Circling back to my previous point, and adding up to Jesse's comment above: which plugins would actually be affected? It is maybe a five-line change to switch the thread context loader¹, and it would be nice to get JAXB out of core if we could. I think I provided some data about "which plugins would actually be affected?": the answer is likely "very few" or something along this. "get JAXB out of core": given my testing on sloccount-plugin, I think this is possible. Now, I'm aware I've not tested the whole Jenkins ecosystem, but so I'm still wondering if this subject is as prevalent as we were imagining. I guess, again, the fact many fixes were pushed already makes this less and less of an issue. I'm eager to hear what people think.
[JIRA] (JENKINS-55627) Display Links to DT Server
Title: Message Title Mark Symons created an issue Jenkins / JENKINS-55627 Display Links to DT Server Issue Type: Improvement Assignee: Steve Springett Components: dependency-track-plugin Created: 2019-01-16 17:34 Priority: Minor Reporter: Mark Symons Dependency-Track plugin should display links from the Jenkins job to the relevent Dependency-Track Server project. Such links would ease process: allow instant navigation from Jenkins to the place where one has to perform auditing and management! The links should be provided independent of whether or not "synchronous publishing mode" is enabled. The links should be provided for pipeline jobs and old-style maven/freestyle jobs. Possibly, the enhancement could be extended via incorporation of badges, should Dependency-Track issue 252 be implemented. I am using the plugin in synchronous mode (as advised in the best practice documentation) and the resulting "Dependency-Track" Results are certainly handsome looking. However, there are no links for the listed CVEs, etc, (links which are provided by the Dependency-Check plugin). Maybe that could be the subject of a separate enhancement issue... but if one could just click a link to DT server then all the info would be available there anyway. The above observations are based on usage of: Dependency-Track Server v3.4.0 Jenkins v2.150.1 cyclonedx-maven-plugin v1.3.1 (and cyclonedx-node-module as well)
[JIRA] (JENKINS-55626) Build hangs using inheritFrom without a label
Title: Message Title
Steve Boardwell updated an issue
Jenkins / JENKINS-55626
Build hangs using inheritFrom without a label
Change By:
Steve Boardwell
h3. Problem StatementThe build hangs when using {{inheritFrom}} in a declarative pipeline (have not tested in a script pipeline) and you omit the {{label}} tag. The problem is that there is no information that something is wrong.h3. To ReproduceUse the following (uncomment label to make it work):{noformat}pipeline {agent {kubernetes {inherit>From 'nodejs'// label 'my-agent'containerTemplate {name 'nodejs'image 'jenkinsxio/builder-nodejs8x:0.1.187'}defaultContainer 'nodejs'}}stages {stage('Npm Check') {steps {sh 'npm -v' input 'wait' }}}post {always {cleanWs()}}}{noformat}From the Jenkins log:{noformat}Jan 16, 2019 5:01:51 PM org.jenkinsci.plugins.jx.resources.BuildSyncRunListener upsertBuildINFO: Updated pipeline activity .Jan 16, 2019 5:01:53 PM com.elasticbox.jenkins.k8s.services.task.ScheduledPoolingTask executeINFO: Pooling task: WaitForThePodToBeRunningTask finished successfullyJan 16, 2019 5:01:53 PM com.elasticbox.jenkins.k8s.services.slavesprovisioning.chain.steps.WaitForPodToBeRunning handleINFO: Pod is up and runningJan 16, 2019 5:01:59 PM com.elasticbox.jenkins.k8s.plugin.clouds.KubernetesCloud canProvisionINFO: Checking label: jenkins-jx-base.Jan 16, 2019 5:02:00 PM com.elasticbox.jenkins.k8s.plugin.clouds.KubernetesCloud canProvisionINFO: Checking label: jenkins-swiftJan 16, 2019 5:02:00 PM com.squareup.okhttp.internal.Platform$JdkWithJettyBootPlatform getSelectedProtocolINFO: ALPN callback dropped: SPDY and HTTP/2 are disabled. Is alpn-boot on the boot class path?Jan 16, 2019 5:02:53 PM com.elasticbox.jenkins.k8s.services.task.ScheduledPoolingTask executeSEVERE: Timeout reached(60 secs) executing task: WaitForTheSlaveToBeOnlineTaskJan 16, 2019 5:02:53 PM com.elasticbox.jenkins.k8s.services.slavesprovisioning.chain.steps.WaitForSlaveToBeOnline handleSEVERE: Error waiting for the Jenkins slave to be onlineJan 16, 2019 5:02:53 PM com.elasticbox.jenkins.k8s.services.SlaveProvisioningServiceImpl slaveProvisionSEVERE: Error provisioning Pod Jenkins slaveJan 16, 2019 5:02:57 PM hudson.slaves.NodeProvisioner$2 runWARNING: Unexpected exception encountered while provisioning agent Jenkins Kubernetes Slavecom.elasticbox.jenkins.k8s.services.error.ServiceException: Error waiting for the Jenkins slave to be online at com.elasticbox.jenkins.k8s.services.slavesprovisioning.chain.steps.WaitForSlaveToBeOnline.handle(WaitForSlaveToBeOnline.java:64) at com.elasticbox.jenkins.k8s.services.SlaveProvisioningServiceImpl.slaveProvision(SlaveProvisioningServiceImpl.java:55) at com.elasticbox.jenkins.k8s.plugin.clouds.KubernetesCloud$1.call(KubernetesCloud.java:172) at
[JIRA] (JENKINS-55626) Build hangs using inheritFrom without a label
Title: Message Title
Steve Boardwell created an issue
Jenkins / JENKINS-55626
Build hangs using inheritFrom without a label
Issue Type:
Bug
Assignee:
Carlos Sanchez
Components:
kubernetes-plugin
Created:
2019-01-16 17:30
Environment:
Jenkins ver. 2.150.1 Kubernetes Plugin: 1.13.2
Priority:
Minor
Reporter:
Steve Boardwell
Problem Statement The build hangs when using inheritFrom in a declarative pipeline (have not tested in a script pipeline) and you omit the label tag. The problem is that there is no information that something is wrong. To Reproduce Use the following (uncomment label to make it work):
pipeline {
agent {
kubernetes {
inheritFrom 'nodejs'
// label 'my-agent'
containerTemplate {
name 'nodejs'
image 'jenkinsxio/builder-nodejs8x:0.1.187'
}
defaultContainer 'nodejs'
}
}
stages {
stage('Npm Check') {
steps {
sh 'npm -v'
input 'wait'
}
}
}
post {
always {
cleanWs()
}
}
}
From the Jenkins log:
Jan 16, 2019 5:01:51 PM org.jenkinsci.plugins.jx.resources.BuildSyncRunListener upsertBuild
INFO: Updated pipeline activity .
Jan 16, 2019 5:01:53 PM
[JIRA] (JENKINS-55492) Plugin is not reusing stopped AWS EC2 instances
Title: Message Title Sascha Kettler commented on JENKINS-55492 Re: Plugin is not reusing stopped AWS EC2 instances I might experiencing the same issue. Do you also have multiple subnet ids configured? At least in my case this is the culprit: The DescribeInstancesRequest to look for possible instances filters by ONE subnetId equal to chooseSubnetId() - which will return one of the defined subnets in a round-robin fashion. As I have a subnet per AZ, the first instance will be started (and on idle, stopped) in AZ a. Then, when we need an instance again, chooseSubnetId() will have moved to a different subnet in AZ b - no instances can be found there, so a new one is created. What should happen instead is, that the DescribeInstancesRequest should filter for ANY of the defined subnetIds. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55447) Remote call on JNLP4-connect connection from ... failed
Title: Message Title Jakub Pawlinski commented on JENKINS-55447 Re: Remote call on JNLP4-connect connection from ... failed Sorry, working on it Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55368) No issues found when parsing Eclipse ECJ output from console log during maven build
Title: Message Title
Piotrek Zygielo edited a comment on JENKINS-55368
Re: No issues found when parsing Eclipse ECJ output from console log during maven build
Tiny repo: [github.com/pzrep/ecj-warnings|https://github.com/pzrep/ecj-warnings] Compiled with standard compiler: [https://travis-ci.org/pzrep/ecj-warnings/jobs/480451056] and with warning from ECJ: [https://travis-ci.org/pzrep/ecj-warnings/jobs/480451058#L452] BUT, but, but.. the same file compiled with standalone ecj gives message in slightly different format:{code}ecj ecj/Simple.java --1. WARNING in /home/piotr/.../ecj/Simple.java (at line 4) private int id; ^^The value of the field Simple.id is not used--1 problem (1 warning){code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55625) ec2 agent launching broken in 1.42
Title: Message Title FABRIZIO MANFREDI commented on JENKINS-55625 Re: ec2 agent launching broken in 1.42 Which version of the plugin has been used before the upgrade ? Are specify in the configuration the path of the java or working dir other things ? Did you restart the jenkins without any change in the configuration ? in this case can you re try the plugin, but before the use to save the configuration (without any changes ) ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55220) Multibranch Pipeline jobs get randomly lost
Title: Message Title Joseph Petersen commented on JENKINS-55220 Re: Multibranch Pipeline jobs get randomly lost Jonas Büth I suggest you dedicate time to debug the issue, I am only a maintainer of the plugin, I do not work with Bitbucket directly anymore so it requires more time than I can afford to debug issues. I rely on the community to solve any issues they might experience. If you need guidance on how to get started, please ask away. I suggest you look here: https://wiki.jenkins.io/display/JENKINS/Plugin+tutorial Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55562) Plugin can not be loaded anymore due to JDK Problems
Title: Message Title Jesse Glick updated JENKINS-55562 Jenkins / JENKINS-55562 Plugin can not be loaded anymore due to JDK Problems Change By: Jesse Glick Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55562) Plugin can not be loaded anymore due to JDK Problems
Title: Message Title Jesse Glick stopped work on JENKINS-55562 Change By: Jesse Glick Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55625) ec2 agent launching broken in 1.42
Title: Message Title
Andrew C updated an issue
Jenkins / JENKINS-55625
ec2 agent launching broken in 1.42
Change By:
Andrew C
Upgraded to ec2 plugin 1.42 today (Jenkins 2.150.1) and it broke ec2 agent launching. Downgrading to 1.42 fixed the problem. Here's the exception and stack trace below. We are attempting to launch Linux m4large instances with an init script. Let me know if I can provide more information and thanks for taking a look. {code:java}<===[JENKINS REMOTING CAPACITY]===>Remoting version: 3.27This is a Unix agentERROR: Connection terminatedERROR: Unexpected error in launching an agent. This is probably a bug in Jenkinsjava.io.EOFExceptionat java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2680)at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3155)at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:861)at java.io.ObjectInputStream.(ObjectInputStream.java:357)at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:49)at hudson.remoting.Command.readFrom(Command.java:140)at hudson.remoting.Command.readFrom(Command.java:126)at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:36)at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63)Caused: java.io.IOException: Unexpected termination of the channelat hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:77)java.lang.NullPointerExceptionat hudson.Util.isRelativePath(Util.java:555)at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:642)at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:432)at hudson.plugins.ec2.ssh.EC2UnixLauncher.launchScript(EC2UnixLauncher.java:217)at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:48)at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:294)at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71)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 java.lang.Thread.run(Thread.java:748){code}
[JIRA] (JENKINS-55562) Plugin can not be loaded anymore due to JDK Problems
Title: Message Title Jesse Glick assigned an issue to Raphael Pionke Jenkins / JENKINS-55562 Plugin can not be loaded anymore due to JDK Problems Change By: Jesse Glick Assignee: Jesse Glick Raphael Pionke Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55562) Plugin can not be loaded anymore due to JDK Problems
Title: Message Title Jesse Glick updated JENKINS-55562 Jenkins / JENKINS-55562 Plugin can not be loaded anymore due to JDK Problems Change By: Jesse Glick Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55625) ec2 agent launching broken in 1.42
Title: Message Title
Andrew C updated an issue
Jenkins / JENKINS-55625
ec2 agent launching broken in 1.42
Change By:
Andrew C
Upgraded to ec2 plugin 1.42 today (Jenkins 2.150.1) and it broke ec2 agent launching. Downgrading to 1.42 fixed the problem. Here's the exception and stack trace below. Let me know if I can provide more information and thanks for taking a look. {code:java}<===[JENKINS REMOTING CAPACITY]===>Remoting version: 3.27This is a Unix agentERROR: Connection terminatedERROR: Unexpected error in launching an agent. This is probably a bug in Jenkinsjava.io.EOFExceptionat java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2680)at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3155)at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:861)at java.io.ObjectInputStream.(ObjectInputStream.java:357)at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:49)at hudson.remoting.Command.readFrom(Command.java:140)at hudson.remoting.Command.readFrom(Command.java:126)at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:36)at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63)Caused: java.io.IOException: Unexpected termination of the channelat hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:77) java.lang.NullPointerExceptionat hudson.Util.isRelativePath(Util.java:555)at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:642)at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:432)at hudson.plugins.ec2.ssh.EC2UnixLauncher.launchScript(EC2UnixLauncher.java:217)at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:48)at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:294)at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71)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 java.lang.Thread.run(Thread.java:748){code}
[JIRA] (JENKINS-55625) ec2 agent launching broken in 1.42
Title: Message Title Andrew C created an issue Jenkins / JENKINS-55625 ec2 agent launching broken in 1.42 Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2019-01-16 16:07 Environment: Jenkins 2.150.1 Priority: Minor Reporter: Andrew C Upgraded to ec2 plugin 1.42 today (Jenkins 2.150.1) and it broke ec2 agent launching. Downgrading to 1.42 fixed the problem. Here's the exception and stack trace below. Let me know if I can provide more information and thanks for taking a look. <===[JENKINS REMOTING CAPACITY]===>Remoting version: 3.27 This is a Unix agent ERROR: Connection terminated ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2680) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3155) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:861) at java.io.ObjectInputStream.(ObjectInputStream.java:357) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:49) at hudson.remoting.Command.readFrom(Command.java:140) at hudson.remoting.Command.readFrom(Command.java:126) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:36) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63) Caused: java.io.IOException: Unexpected termination of the channel at
[JIRA] (JENKINS-55368) No issues found when parsing Eclipse ECJ output from console log during maven build
Title: Message Title Piotrek Zygielo commented on JENKINS-55368 Re: No issues found when parsing Eclipse ECJ output from console log during maven build Tiny repo: github.com/pzrep/ecj-warnings Compiled with standard compiler: https://travis-ci.org/pzrep/ecj-warnings/jobs/480451056 and with warning from ECJ: https://travis-ci.org/pzrep/ecj-warnings/jobs/480451058#L452 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55624) Authorize Projects plugin causes no git credentials to be found with 'Run as Specific User' Strategy is set
Title: Message Title Mike Nicholson created an issue Jenkins / JENKINS-55624 Authorize Projects plugin causes no git credentials to be found with 'Run as Specific User' Strategy is set Issue Type: Bug Assignee: ikedam Attachments: run_as_specific_user.png, run_as_user_who_triggered.png Components: authorize-project-plugin Created: 2019-01-16 16:01 Environment: Jenkins ver 2.157, running in a container Authorize Project 1.3.0 Credentials Plugin 2.1.18 Git Client 2.7.4 Priority: Minor Reporter: Mike Nicholson When attempting to configure source control for a freestyle job with the Build Authorization Strategy set to 'Run as Specific User', I don't see any available git credentials. I have credentials installed and they appear when I set Build Authorization Strategy to "Run as User who Triggered Build". See attached images. However, if I set the Build Authorization Strategy to "Run as User who Triggered", configure my job with the proper credentials and then switch to "Run as specific user", everything works, but when I go to configure the job the git credentials section of the config page displays the error that the currently configured credentials cannot be found. This is an ugly workaround but it does let my job run as desired. Steps to Reproduce: Install Authorize Project Configure Global Security > Access Control for Builds and to allow Per-project configurable build
