[JIRA] (JENKINS-37437) Pipeline integration for OWASP checker
Title: Message Title Itai Sanders commented on JENKINS-37437 Re: Pipeline integration for OWASP checker Hi, any news with the pipeline support? I want to incorporate this tool into our pipelines and figured I might be able to run this as a command line tool and then publish the results using the already supported publisher. but if there's a chance to have a native builder to manage the test-run it would be preferable. Thanks. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38657) Make this available as a pipeline step
Title: Message Title Itai Sanders commented on JENKINS-38657 Re: Make this available as a pipeline step and if possible - receive the triggered console output as the returned object. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35337) Finds credentials but unable to read key: null
Title: Message Title Itai Sanders commented on JENKINS-35337 Re: Finds credentials but unable to read key: null UPDATE: ok, I used the complete ppk file and it works now. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35337) Finds credentials but unable to read key: null
Title: Message Title Itai Sanders edited a comment on JENKINS-35337 Re: Finds credentials but unable to read key: null UPDATE: ok, I used the complete ppk file and it works now. I guess the problem is just in the PEM format. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35337) Finds credentials but unable to read key: null
Title: Message Title
Itai Sanders edited a comment on JENKINS-35337
Re: Finds credentials but unable to read key: null
I had the same problem (plugin version 1 . 13). I think I got passed it when I enclosed the private key with the opening and closing statement:{code}-BEGIN RSA PRIVATE KEY-AAABARwm...ggrkQs8=-END RSA PRIVATE KEY-{code}but then the error changed to:{code}[ssh-agent] Looking for ssh-agent implementation...[ssh-agent] Java/JNR ssh-agent[ssh-agent] Registered BouncyCastle on the remote agent[ssh-agent] Unable to read key: problem creating RSA private key: java.lang.IllegalArgumentException: failed to construct sequence from byte[]: unexpected end-of-contents markerorg.bouncycastle.openssl.PEMException: problem creating RSA private key: java.lang.IllegalArgumentException: failed to construct sequence from byte[]: unexpected end-of-contents marker at org.bouncycastle.openssl.PEMParser$KeyPairParser.parseObject(Unknown Source) at org.bouncycastle.openssl.PEMParser.readObject(Unknown Source) at jenkins.bouncycastle.api.PEMEncodable.decode(PEMEncodable.java:153) at com.cloudbees.jenkins.plugins.sshagent.jna.JNRRemoteAgent.addIdentity(JNRRemoteAgent.java:79) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:887) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:862) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:821) at hudson.remoting.UserRequest.perform(UserRequest.java:153) at hudson.remoting.UserRequest.perform(UserRequest.java:50) at hudson.remoting.Request$2.run(Request.java:332) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)Caused by: org.bouncycastle.openssl.PEMException: problem creating RSA private key: java.lang.IllegalArgumentException: failed to construct sequence from byte[]: unexpected end-of-contents marker at org.bouncycastle.openssl.PEMParser$RSAKeyPairParser.parse(Unknown Source) ... 19 moreCaused by: java.lang.IllegalArgumentException: failed to construct sequence from byte[]: unexpected end-of-contents marker at org.bouncycastle.asn1.ASN1Sequence.getInstance(Unknown Source) ... 20 more[ssh-agent] Started.{code}needless to say that the {{sh 'ssh user@host'}} inside the {{sshagent}} scope fails.
Add Comment
[JIRA] (JENKINS-35337) Finds credentials but unable to read key: null
Title: Message Title Itai Sanders commented on JENKINS-35337 Re: Finds credentials but unable to read key: null I had the same problem. I think I got passed it when I enclosed the private key with the opening and closing statement: -BEGIN RSA PRIVATE KEY- AAABARwm ...ggrkQs8= -END RSA PRIVATE KEY- but then the error changed to: [ssh-agent] Looking for ssh-agent implementation... [ssh-agent] Java/JNR ssh-agent [ssh-agent] Registered BouncyCastle on the remote agent [ssh-agent] Unable to read key: problem creating RSA private key: java.lang.IllegalArgumentException: failed to construct sequence from byte[]: unexpected end-of-contents marker org.bouncycastle.openssl.PEMException: problem creating RSA private key: java.lang.IllegalArgumentException: failed to construct sequence from byte[]: unexpected end-of-contents marker at org.bouncycastle.openssl.PEMParser$KeyPairParser.parseObject(Unknown Source) at org.bouncycastle.openssl.PEMParser.readObject(Unknown Source) at jenkins.bouncycastle.api.PEMEncodable.decode(PEMEncodable.java:153) at com.cloudbees.jenkins.plugins.sshagent.jna.JNRRemoteAgent.addIdentity(JNRRemoteAgent.java:79) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:887) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:862) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:821) at hudson.remoting.UserRequest.perform(UserRequest.java:153) at hudson.remoting.UserRequest.perform(UserRequest.java:50) at hudson.remoting.Request$2.run(Request.java:332) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: org.bouncycastle.openssl.PEMException: problem creating RSA private key: java.lang.IllegalArgumentException: failed to construct sequence from byte[]: unexpected end-of-contents marker at org.bouncycastle.openssl.PEMParser$RSAKeyPairParser.parse(Unknown Source) ... 19 more Caused by: java.lang.IllegalArgumentException: failed to construct sequence from byte[]: unexpected end-of-contents marker at org.bouncycastle.asn1.ASN1Sequence.getInstance(Unknown Source) ... 20 more [ssh-agent] Started. needless to say that the sh 'ssh user@host' inside the sshagent scope fails.
[JIRA] (JENKINS-38157) multiple new errors on long time running pipelines after latest update
Title: Message Title Itai Sanders commented on JENKINS-38157 Re: multiple new errors on long time running pipelines after latest update Jesse Glick: I have read the pipeline tutorials, and I already have quite a few NonCPS methods in my scripts. I find it hard to simply dispose this as "bad scripting" when these scripts were running cleanly since the first days of Jenkins 2.0 without any sign of NotSerializableException in mid run nor run end. up until the mentioned update that is. I do accept that there might be some policy change during that update that would change script behavior. wouldn't be the first time it happens, in fact. I will see how I can work around it, but at the end of the day there is a limit how much you can do in a NonCPS method (since we cannot call DSL methods inside). I would admit that I was going to ask you to add a mention of this to the change log, since when I installed the updates the day they were released I went though it and didn't see any indication for such risk, but a quick recheck already confirmed that you did add this exact line. I guess I jumped on the upgdate a few hours too soon, being the updatoholic that I am. thanks for the clarification, this is super important, as you well know. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33507) Bitbucket Server webhooks and Bitbucket Cloud build status notifications
Title: Message Title Itai Sanders commented on JENKINS-33507 Re: Bitbucket Server webhooks and Bitbucket Cloud build status notifications does this mean we also have the build status notification fixed? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38157) multiple new errors on long time running pipelines after latest update
Title: Message Title
Itai Sanders updated an issue
Jenkins / JENKINS-38157
multiple new errors on long time running pipelines after latest update
Change By:
Itai Sanders
we updated the pipeline plugins to the latest versions and noticed that after the upgrade a few of our critical and up-until-now working pipelines started crashing with different messages errors.downgrading to Pipeline: Groovy 2.13 and Pipeline: Shared Groovy Libraries 2.2 fixed most of the errors.example errors that were solved:{code}java.io.NotSerializableException: java.util.AbstractList$Itr at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:860) at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1032) at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:988) at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:854) at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1032) at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:988) at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:854) at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1032) at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:988) at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:854) at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1032) at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:988) at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:967) at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:854) at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1032) at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:988) at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:854) at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1032) at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:988) at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:967) at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:854) at org.jboss.marshalling.river.BlockMarshaller.doWriteObject(BlockMarshaller.java:65) at org.jboss.marshalling.river.BlockMarshaller.writeObject(BlockMarshaller.java:56) at org.jboss.marshalling.MarshallerObjectOutputStream.writeObjectOverride(MarshallerObjectOutputStream.java:50) at org.jboss.marshalling.river.RiverObjectOutputStream.writeObjectOverride(RiverObjectOutputStream.java:179) at java.io.ObjectOutputStream.writeObject(Unknown Source) at java.util.HashMap.internalWriteEntries(Unknown Source) at java.util.HashMap.writeObject(Unknown
[JIRA] (JENKINS-38157) multiple new errors on long time running pipelines after latest update
Title: Message Title Itai Sanders updated an issue Jenkins / JENKINS-38157 multiple new errors on long time running pipelines after latest update Change By: Itai Sanders Component/s: workflow-cps-global-lib-plugin Component/s: workflow-cps-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38157) multiple new errors on long time running pipelines after latest update
Title: Message Title Itai Sanders created an issue Jenkins / JENKINS-38157 multiple new errors on long time running pipelines after latest update Issue Type: Bug Assignee: Jesse Glick Components: pipeline Created: 2016/Sep/13 7:46 AM Environment: Jenkins 2.21 Pipeline: Groovy 2.15 Pipeline: Shared Groovy Libraries 2.3 Priority: Blocker Reporter: Itai Sanders we updated the pipeline plugins to the latest versions and noticed that after the upgrade a few of our critical and up-until-now working pipelines started crashing with different messages errors. downgrading to Pipeline: Groovy 2.13 and Pipeline: Shared Groovy Libraries 2.2 fixed most of the errors. example errors that were solved: java.io.NotSerializableException: java.util.AbstractList$Itr at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:860) at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1032) at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:988) at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:854) at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1032) at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:988) at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:854) at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1032) at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:988) at org.jboss.marshalli
[JIRA] (JENKINS-36225) load step causes changes to parameters to be discarded
Title: Message Title
Itai Sanders commented on JENKINS-36225
Re: load step causes changes to parameters to be discarded
ok, I double checked. this doesn't happen with "normal" global variables, but only when retrieving those from build parameters. to reproduce, run the following pipeline code:
stage 'setting build parameters'
properties([parameters([string(defaultValue: 'SomeValue', description: '', name: 'GV')])])
node {
stage 'preparing file system'
deleteDir()
writeFile file: 'myscript.groovy', text: '''
echo 'script loaded.'
'''
stage 'edditing parameter variable'
echo "$GV"
GV = GV - 'Some'
echo "$GV"
stage 'running loading step'
load 'myscript.groovy'
stage 'result'
echo "$GV"
if (GV != 'Value')
currentBuild.result = 'UNSTABLE'
deleteDir()
}
you will need to run it twice, once to set the build parameter and the next one to use it. I get the following output:
Entering stage setting build parameters
Proceeding
[Pipeline] properties
[Pipeline] node
Running on...
[Pipeline] {
[Pipeline] stage (preparing file system)
Entering stage preparing file system
Proceeding
[Pipeline] deleteDir
[Pipeline] writeFile
[Pipeline] stage (edditing parameter variable)
Entering stage edditing parameter variable
Proceeding
[Pipeline] echo
SomeValue
[Pipeline] echo
Value
[Pipeline] stage (running loading step)
Entering stage running loading step
Proceeding
[Pipeline] load
[Pipeline] { (myscript.groovy)
[Pipeline] echo
script loaded.
[Pipeline] }
[Pipeline] // load
[Pipeline] stage (result)
Entering stage result
Proceeding
[Pipeline] echo
SomeValue
[Pipeline] deleteDir
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
[Bitbucket] Notifying commit build result
[Bitbucket] Build result notified
Finished: UNSTABLE
Add Comment
[JIRA] (JENKINS-36225) load step causes changes to parameters to be discarded
Title: Message Title Itai Sanders commented on JENKINS-36225 Re: load step causes changes to parameters to be discarded Jesse Glick I posted a pseudo-script for reproduction. I agree about the lexical variables preferences, but build parameters are passed as global variables (the scenario in which I've had the problem with in the first place). I didn't check this our for a while now (worked around it in my pipelines by reassigning the variables after each load step). I will try making sure this wasn't fixed along some other update and let you know the result. will post the actual script too if the problem still exists. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33841) Support for pipeline builds
Title: Message Title Itai Sanders commented on JENKINS-33841 Re: Support for pipeline builds that would be great Allan BURDAJEWICZ! btw, I didn't get to test it myself (since I am using my locally compiled merged version), but I think if you don't use the default parameters of the plugin and define your own legal parameters manually, you would work around this bug (along with the "key per job and not per build" sort-of-a-bug). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33841) Support for pipeline builds
Title: Message Title Itai Sanders commented on JENKINS-33841 Re: Support for pipeline builds Yevhenii Kurtov I think you are gettin mixed up. you need to provide credentials to your repository in order to access it. you can either: 1. provide them in the job configurations (and place the Jenkinsfile inside the scm), in which case you can simply call on 'scm checkout' to checkout the entire code. Jenkins then will use the credentials you used to access the Jenkinsfile in order to checkout that same repo. 2. provide them inside the checkout call, as you first did, in case you are writing your pipeline code inside Jenkins (so you never configured the scm in the job configurations) or in case you wish to checkout a different repo than the one you used to store the Jenkinsfile. either way, you will still need to provide the notifier plugin with the credentials to mark the build status. you configure it inside the Jenkins Configure System (inside Manage Jenkins, not in the specific job). you will need to produce a dedicated OAuth credentials. this and more you can find in the very good README in github: https://github.com/jenkinsci/bitbucket-build-status-notifier-plugin and again - this is getting much more general than the discussed issue. you should raise those questions in Slack, or if you want you can Telegram me and I wouldn't mind helping you out as far as I can. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsu
[JIRA] (JENKINS-33841) Support for pipeline builds
Title: Message Title Itai Sanders commented on JENKINS-33841 Re: Support for pipeline builds Yevhenii Kurtov now you have a Credentials not Found exception. did you set them in the Jenkins Global Configurations? if you want some general help with Jenkins maybe it will be better to move to a more general platform e.g. https://devopsengineers.slack.com/archives/jenkins-ci (once there, feel free to pm me if you'd like. although I do follow the jenkins-ci channel anyway) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33841) Support for pipeline builds
Title: Message Title Itai Sanders commented on JENKINS-33841 Re: Support for pipeline builds Yevhenii Kurtov: I need to see the pipeline code to be certain, but from the snippet you posted it seems like you activated the bitbucketnotifier before the checkout stage. Proceeding [Pipeline] bitbucketStatusNotify [Pipeline] stage (Checkout) the notifier is looking for the scm object instance, which in pipelines (unlike the freestyle jobs) is only initiated when you go through the scm checkout step, so basically you are calling for bitbucketnotifier with an uninitiated (null) scm object. it might be best if the plugin catches this and posts a more friendly exception message. maybe I'll look into it and post another pull request later if no one gets to it. let me know if placing the scm checkout before the bitbucketnotifier step worked or it's something else entirely. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33841) Support for pipeline builds
Title: Message Title Itai Sanders commented on JENKINS-33841 Re: Support for pipeline builds no problem. I am using my own locally compiled version with both my pull requests here, since I needed those fixes. I'm sorry about the versions mixup. tbh, this is the first time I am doing an actual pull request to a Jenkins plugin and I just changed the code as needed without taking notice of the metadata that came with it. I guess you can just commit whatever needs to be changed in the versions, or give me the pointers and I'll be glad to add them to the pull request. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33841) Support for pipeline builds
Title: Message Title
Itai Sanders edited a comment on JENKINS-33841
Re: Support for pipeline builds
[~flagbit] - sure:{code}Jul 18, 2016 11:43:00 AM INFO hudson.model.Queue maintainBuildableItem devops.tests.allsorts: pending -> buildable as the assigned executor disappearedJul 18, 2016 11:43:46 AM WARNING org.jenkinsci.plugins.workflow.support.steps.input.InputAction loadExecutionsno flow execution found for devops.tests.allsorts/notifier #7Jul 18, 2016 11:45:33 AM INFO org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusHelper sendBuildStatusNotificationThis request was sent: { "state": "INPROGRESS", "key": "[some key]", "url": "[jenkins url]/job/devops.tests.allsorts/job/notifier/8/", "name": "devops.tests.allsorts » notifier #8"}Jul 18, 2016 11:45:33 AM INFO org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusHelper sendBuildStatusNotificationThis response was received: Bad RequestJul 18, 2016 11:45:59 AM INFO org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusHelper sendBuildStatusNotificationThis request was sent: { "state": "SUCCESSFUL", "key": "[same key as previous request]", "url": "[jenkins url]job/devops.tests.allsorts/job/notifier/8/", "name": "devops.tests.allsorts » notifier #8"}Jul 18, 2016 11:45:59 AM INFO org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusHelper sendBuildStatusNotificationThis response was received: Bad RequestJul 18, 2016 11:45:59 AM INFO org.jenkinsci.plugins.workflow.job.WorkflowRun finishdevops.tests.allsorts/notifier #8 completed: SUCCESS{code}maybe it's the » sign that comes from the folder plugin.as an afterthought, I decided to check this out on a job outside any foldered structure (such as in a multibranch job) and there it worked (same repo so same Jenkinsfile). moved that job into a folder, and again I get the same results as the multibranch job.so whatever it is - it happens only when ran inside a folder. EDIT: I took the liberty of forking the code and look into it myself. it wasn't such a huge fix. created a [pull request|https://github.com/jenkinsci/bitbucket-build-status-notifier-plugin/pull/30] for you.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-33841) Support for pipeline builds
Title: Message Title Itai Sanders commented on JENKINS-33841 Re: Support for pipeline builds btw, I also noticed that if I notify about an INPROGRESS status and the build fails or aborted, then there's no automatic status update in Bitbucket so it freezes on INPROGRESS. not a show stopper, but something to think about for a future release. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33841) Support for pipeline builds
Title: Message Title
Itai Sanders commented on JENKINS-33841
Re: Support for pipeline builds
Antonio Mansilla - sure:
Jul 18, 2016 11:43:00 AM INFO hudson.model.Queue maintain
BuildableItem devops.tests.allsorts: pending -> buildable as the assigned executor disappeared
Jul 18, 2016 11:43:46 AM WARNING org.jenkinsci.plugins.workflow.support.steps.input.InputAction loadExecutions
no flow execution found for devops.tests.allsorts/notifier #7
Jul 18, 2016 11:45:33 AM INFO org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusHelper sendBuildStatusNotification
This request was sent: {
"state": "INPROGRESS",
"key": "[some key]",
"url": "[jenkins url]/job/devops.tests.allsorts/job/notifier/8/",
"name": "devops.tests.allsorts » notifier #8"
}
Jul 18, 2016 11:45:33 AM INFO org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusHelper sendBuildStatusNotification
This response was received: Bad Request
Jul 18, 2016 11:45:59 AM INFO org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusHelper sendBuildStatusNotification
This request was sent: {
"state": "SUCCESSFUL",
"key": "[same key as previous request]",
"url": "[jenkins url]job/devops.tests.allsorts/job/notifier/8/",
"name": "devops.tests.allsorts » notifier #8"
}
Jul 18, 2016 11:45:59 AM INFO org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusHelper sendBuildStatusNotification
This response was received: Bad Request
Jul 18, 2016 11:45:59 AM INFO org.jenkinsci.plugins.workflow.job.WorkflowRun finish
devops.tests.allsorts/notifier #8 completed: SUCCESS
maybe it's the » sign that comes from the folder plugin. as an afterthought, I decided to check this out on a job outside any foldered structure (such as in a multibranch job) and there it worked (same repo so same Jenkinsfile). moved that job into a folder, and again I get the same results as the multibranch job. so whatever it is - it happens only when ran inside a folder.
Add Comment
[JIRA] (JENKINS-33841) Support for pipeline builds
Title: Message Title
Itai Sanders edited a comment on JENKINS-33841
Re: Support for pipeline builds
[~amansilla] - thanks for the update!I updated the plugin and ran a small test in a multibranch job using the following Jenkinsfile:{code}node {stage 'checkout'checkout scmbitbucketStatusNotify ( buildState: 'INPROGRESS' )}stage 'pause'input 'waiting...'stage 'complete'bitbucketStatusNotify ( buildState: 'SUCCESSFUL' ){code}the console output in Jenkins seems promising:{code}Branch indexing[Pipeline] nodeRunning on master...[Pipeline] {[Pipeline] stage (checkout)Entering stage checkoutProceeding[Pipeline] checkout...[Pipeline] bitbucketStatusNotifySending build status INPROGRESS for commit 4e7eb185a08b8b5cb1775c31d26f3f05cbaa8bbc to BitBucket is done![Pipeline] }[Pipeline] // node[Pipeline] stage (pause)Entering stage pauseProceeding[Pipeline] inputwaiting...Proceed or AbortApproved by Itai Sanders[Pipeline] stage (complete)Entering stage completeProceeding[Pipeline] bitbucketStatusNotifySending build status SUCCESSFUL for commit 4e7eb185a08b8b5cb1775c31d26f3f05cbaa8bbc to BitBucket is done![Pipeline] End of Pipeline[Bitbucket] Notifying commit build result[Bitbucket] Build result notifiedFinished: SUCCESS{code}but when I go to the Bitbucket web interface I can't see any sign of the build status: !screenshot-1.png|thumbnail! am I doing it wrong? just for some more details: I tested this with both a consumer under my own account and a consumer under my team's account. both had the same result.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the
[JIRA] (JENKINS-33841) Support for pipeline builds
Title: Message Title
Itai Sanders commented on JENKINS-33841
Re: Support for pipeline builds
Antonio Mansilla - thanks for the update! I updated the plugin and ran a small test in a multibranch job using the following Jenkinsfile:
node {
stage 'checkout'
checkout scm
bitbucketStatusNotify ( buildState: 'INPROGRESS' )
}
stage 'pause'
input 'waiting...'
stage 'complete'
bitbucketStatusNotify ( buildState: 'SUCCESSFUL' )
the console output in Jenkins seems promising:
Branch indexing
[Pipeline] node
Running on master...
[Pipeline] {
[Pipeline] stage (checkout)
Entering stage checkout
Proceeding
[Pipeline] checkout
...
[Pipeline] bitbucketStatusNotify
Sending build status INPROGRESS for commit 4e7eb185a08b8b5cb1775c31d26f3f05cbaa8bbc to BitBucket is done!
[Pipeline] }
[Pipeline] // node
[Pipeline] stage (pause)
Entering stage pause
Proceeding
[Pipeline] input
waiting...
Proceed or Abort
Approved by Itai Sanders
[Pipeline] stage (complete)
Entering stage complete
Proceeding
[Pipeline] bitbucketStatusNotify
Sending build status SUCCESSFUL for commit 4e7eb185a08b8b5cb1775c31d26f3f05cbaa8bbc to BitBucket is done!
[Pipeline] End of Pipeline
[Bitbucket] Notifying commit build result
[Bitbucket] Build result notified
Finished: SUCCESS
but when I go to the Bitbucket web interface I can't see any sign of the build status: am I doing it wrong?
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-33841) Support for pipeline builds
Title: Message Title Itai Sanders updated an issue Jenkins / JENKINS-33841 Support for pipeline builds Change By: Itai Sanders Attachment: screenshot-1.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36225) load step causes changes to parameters to be discarded
Title: Message Title Itai Sanders created an issue Jenkins / JENKINS-36225 load step causes changes to parameters to be discarded Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 2016/Jun/26 1:08 PM Priority: Minor Reporter: Itai Sanders I have a pipeline job which gets some string (choice) parameters. along the pipeline I edit one of those strings, and later on load a groovy script file using the load step. I noticed that the changes I made to the string hold just until the load step, and after that the variable somehow reverts back to the original value (as chosen when the build was initialized). e.g. parameter name: SomeParameter parameter value: SomeValue pipeline script: echo SomeParameter SomeParameter = SomeParameter - 'Some' echo SomeParameter load file: 'myscript.groovy' echo SomeParameters output: [pipeline] echo SomeValue [pipeline] echo Value [pipeline] load [pipeline] echo SomeValue Add Comment
[JIRA] (JENKINS-33841) Support for pipeline builds
Title: Message Title Itai Sanders edited a comment on JENKINS-33841 Re: Support for pipeline builds I tried this plugin for the first time. I defined the OAuth in the Jenkins Global Configurations and it seems like it applied itself by default to my pipelines, which is good.what is strange is that instead of updating the build status in BitBucket, it posts a comment on that commit saying whether it looks good or failed with a link to that build. the build status icon stays empty. EDIT: it seems like the comments don't come from this plugin, but from the BitBucket Source plugin. and they too have an issue requesting for it to become a status update: [JENKINS-33507|https://issues.jenkins-ci.org/browse/JENKINS-33507] Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33841) Support for pipeline builds
Title: Message Title Itai Sanders commented on JENKINS-33841 Re: Support for pipeline builds I tried this plugin for the first time. I defined the OAuth in the Jenkins Global Configurations and it seems like it applied itself by default to my pipelines, which is good. what is strange is that instead of updating the build status in BitBucket, it posts a comment on that commit saying whether it looks good or failed with a link to that build. the build status icon stays empty. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multi-branch-project-plugin] (JENKINS-35460) Multibranch Plugin: branch indexing causes java heap out of space error
Title: Message Title Itai Sanders commented on JENKINS-35460 Re: Multibranch Plugin: branch indexing causes java heap out of space error just an update on our situation that might shed some light on this: I went to the .git dirs inside the cache dir and compared the on of the problematic repo to one of the others. I found that some files were missing, probably files that should be created in the initial fetch that was broken in mid process. I copied FETCH_HEAD, logs/, objects/ and refs/ from my own local (working copy) .git of the same repo into the jenkins cache one and ran another branch indexing. I guess it recognized the files and skipped the initial fetch straight to the update process since everything seems to work now. I made sure that it now recognizes new branches and everything seems to work fine. to validate this I the deleted the cached dir and the branch indexing indeed crashed again like before, leaving behind a half built dir. I copied back the above file and dirs and everything started working normally again. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multi-branch-project-plugin] (JENKINS-35460) Multibranch Plugin: branch indexing causes java heap out of space error
Title: Message Title
Itai Sanders updated an issue
Jenkins / JENKINS-35460
Multibranch Plugin: branch indexing causes java heap out of space error
Change By:
Itai Sanders
we are migrating our jobs to the multibranch pipelines, about a dozen or more.all of them work fine, but one repository wouldn't pass the branch indexing process. the process gets stuck and eventually fails with the following log message: ?? {noformat} Setting origin to https://git.Fetching origin...Finished: NOT_BUILT ?? {noformat} after double and triple checking all our configurations and repositories, we couldn't find any difference between this repository and the others. I went through the Jenkins Log and found out that whenever this particular branch indexing fails the log prints out a java heap out of memory error.it doesn't show the full message on every such error, so I can only assume the first one of those is the relevant full stack trace:{noformat}Jun 08, 2016 11:31:22 AM SEVERE hudson.model.Executor finish1Executor threw an exceptionjava.lang.OutOfMemoryError: Java heap space at org.eclipse.jgit.internal.storage.pack.BinaryDelta.apply(BinaryDelta.java:163) at org.eclipse.jgit.internal.storage.pack.BinaryDelta.apply(BinaryDelta.java:118) at org.eclipse.jgit.transport.PackParser.resolveDeltas(PackParser.java:610) at org.eclipse.jgit.transport.PackParser.resolveDeltas(PackParser.java:587) at org.eclipse.jgit.transport.PackParser.resolveDeltas(PackParser.java:550) at org.eclipse.jgit.transport.PackParser.parse(PackParser.java:507) at org.eclipse.jgit.internal.storage.file.ObjectDirectoryPackParser.parse(ObjectDirectoryPackParser.java:194) at org.eclipse.jgit.transport.PackParser.parse(PackParser.java:448) at org.eclipse.jgit.transport.BasePackFetchConnection.receivePack(BasePackFetchConnection.java:762) at org.eclipse.jgit.transport.BasePackFetchConnection.doFetch(BasePackFetchConnection.java:363) at org.eclipse.jgit.transport.TransportHttp$SmartHttpFetchConnection.doFetch(TransportHttp.java:783) at org.eclipse.jgit.transport.BasePackFetchConnection.fetch(BasePackFetchConnection.java:301) at org.eclipse.jgit.transport.BasePackFetchConnection.fetch(BasePackFetchConnection.java:291) at org.eclipse.jgit.transport.FetchProcess.fetchObjects(FetchProcess.java:247) at org.eclipse.jgit.transport.FetchProcess.executeImp(FetchProcess.java:160) at org.eclipse.jgit.transport.FetchProcess.execute(FetchProcess.java:122) at org.eclipse.jgit.transport.Transport.fetch(Transport.java:1138) at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:130) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.fetch(JGitAPIImpl.java:678) at jenkins.plugins.git.AbstractGitSCMSource.retrieve(AbstractGitSCMSource.java:174) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:146) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:294) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:157) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:122) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410){noformat}again - we have no idea what makes the difference. the repository itself isn't bigger than the others, we don't have spe
[JIRA] [multi-branch-project-plugin] (JENKINS-35460) Multibranch Plugin: branch indexing causes java heap out of space error
Title: Message Title Itai Sanders created an issue Jenkins / JENKINS-35460 Multibranch Plugin: branch indexing causes java heap out of space error Issue Type: Bug Assignee: Matthew DeTullio Components: multi-branch-project-plugin Created: 2016/Jun/08 9:02 AM Environment: master runs on Windows Server 2012 Jenkins 2.8 Priority: Major Reporter: Itai Sanders we are migrating our jobs to the multibranch pipelines, about a dozen or more. all of them work fine, but one repository wouldn't pass the branch indexing process. the process gets stuck and eventually fails with the following log message: ??Setting origin to https://git. Fetching origin... Finished: NOT_BUILT?? after double and triple checking all our configurations and repositories, we couldn't find any difference between this repository and the others. I went through the Jenkins Log and found out that whenever this particular branch indexing fails the log prints out a java heap out of memory error. it doesn't show the full message on every such error, so I can only assume the first one of those is the relevant full stack trace: Jun 08, 2016 11:31:22 AM SEVERE hudson.model.Executor finish1 Executor threw an exception java.lang.OutOfMemo
[JIRA] [workflow-plugin] (JENKINS-34230) Display the reason when branch indexing fails
Title: Message Title Itai Sanders commented on JENKINS-34230 Re: Display the reason when branch indexing fails I get this message as well. and it's the strangest thing, because I have a dozen other repositories where everything works great (so it's not a memory issue), and even this repository works ok on a singlebranch pipeline, but the multibranch pipeline just wouldn't fetch origin. we double and triple checked that all the repositories and all the pipelines are configured identically and still can't find what makes this repository fail the fetch. some sort of informative message could save us a lot of time and grief. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-34745) Check Updates PeriodicWork dies horribly in the case of invalid signature
Title: Message Title Itai Sanders commented on JENKINS-34745 Re: Check Updates PeriodicWork dies horribly in the case of invalid signature this exceptions happens here on a daily basis, seems like some sort of idle process that throws it in a very different context. the exception causes Jenkins to enter a java.lang.OutOfMemoryError: Java heap space spiral from this point onward until the service crashes and must be restarted manually. change Priority to critical because of the daily crash. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-34745) Check Updates PeriodicWork dies horribly in the case of invalid signature
Title: Message Title Itai Sanders updated an issue Jenkins / JENKINS-34745 Check Updates PeriodicWork dies horribly in the case of invalid signature Change By: Itai Sanders Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [youtrack-plugin] (JENKINS-34023) error in parsing comment on git commits
Title: Message Title Itai Sanders created an issue Jenkins / JENKINS-34023 error in parsing comment on git commits Issue Type: Bug Assignee: Erik Zielke Components: youtrack-plugin Created: 2016/Apr/05 12:15 PM Priority: Major Reporter: Itai Sanders when sending a hashtaged issue id inside a commit's comment, it parses the first id and then sends the rest of the comment string as the command, causing multiple issues: 1. cannot send command comment to youtrack, since the comment is parsed as the command (even on new line) and thus returns an error. 2. cannot send multiple commands since all commands are considered as a single command string and thus return an error. 3. cannot update multiple issues since the other hashtaged ids are also parsed as the command string and thus return an error. I tested it with various formats, including those defined for teamcity in the documentation, and all resulted with the above error. The bottom line is that the only format I managed to successfully activate is to finish my comment with "#DO-1 fixed". anything else throws an error. this should be fixed to allow the above actions. if there is a working format I couldn't find, it should be explained in the documentation. Thanks, Itai
[JIRA] [youtrack-plugin] (JENKINS-31874) cannot update 'Fixed in build' field of youtrack with current build number
Title: Message Title Itai Sanders commented on JENKINS-31874 Re: cannot update 'Fixed in build' field of youtrack with current build number I was experiencing the same problem. I looked into it, and it says that YouTrack deprecated the Bundles on their latest upgrade. Any chance to change this feature to update a CustomField as this seems to be the native replacement for it. I myself am trying to do just that - use Jenkins to add a new variable to a global enum field. Thanks, Itai Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
