[JIRA] (JENKINS-51218) EMail-Ext does not send email, because or empty recipients
Title: Message Title
Zack Snyder commented on JENKINS-51218
Re: EMail-Ext does not send email, because or empty recipients
Mark Waite It still does not work. The other error is:
WorkflowScript: 75: expecting '}', found ',' @ line 75, column 100.
DISPLAY_NAME} - ' + currResult,
The retrieve of the email address does not work perfectly, I get in fact the whole command back:
def author_email = bat(returnStdout:true, script:'git log -n 1 --pretty=format:%%ae')
echo "author E-mail is ${author_email}"
Leads to following output:
author E-mail is
G:\jenkins\workspace\app_test-email-branch-27DKLR7UW4OLTKKVCAORJQDJDVIHVIRGU2SWE3JRP7LEG3QEVBWQ>git log -n 1 --pretty=format:%ae
u...@mail.de
What do you think?
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-51218) EMail-Ext does not send email, because or empty recipients
Title: Message Title
Zack Snyder commented on JENKINS-51218
Re: EMail-Ext does not send email, because or empty recipients
Mark Waite Okay, with some minor changes I can retrive the mail address. However, how can I use it with ext-mail?
def author_email = bat(returnStdout:true, script:'git log -n 1 --pretty=format:%%ae')
echo "author E-mail is ${author_email}"
def currResult = getResultAsString(currentBuild)
def prevResult = getResultAsString(currentBuild.getPreviousBuild())
if (currResult != "SUCCESS" || prevResult != "SUCCESS")
{
echo 'send mail'
emailext body: '''${SCRIPT, template="xion-html.template"}''',
recipientProviders: [[$class: 'DevelopersRecipientProvider'],
[$class: 'CulpritsRecipientProvider'],
[$class: 'UpstreamComitterRecipientProvider']
] ${author_email},
subject: '[Jenkins]: ${JOB_NAME} ${BUILD_DISPLAY_NAME} - ' + currResult,
mimeType: 'text/html'
}
I got following error:
WorkflowScript: 74: expecting '}', found ',' @ line 74, column 66.
] ${author_email},
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-51218) EMail-Ext does not send email, because or empty recipients
Title: Message Title
Zack Snyder edited a comment on JENKINS-51218
Re: EMail-Ext does not send email, because or empty recipients
[~markewaite]Okay, you say I can get the email address of the user how who changed the code with {{git log -n 1}}I am new to jenkins and do not understand how to do it properly.Can you please show me the complete code, see the pipeline script above how I send the email, can you adjust it? PS: IMHO, I think the git scm plugin should return this info, creating a branch, with no changes is one thing, but creating a branch with changes, it is clear for me that this are changes.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google 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-51218) EMail-Ext does not send email, because or empty recipients
Title: Message Title
Zack Snyder edited a comment on JENKINS-51218
Re: EMail-Ext does not send email, because or empty recipients
[~markewaite]Okay, you can say I can get the email address of the user how changed the code with {{git log -n 1}}I am new to jenkins and do not understand how to do it properly.Can you please show me the complete code, see the pipeline script above how I send the email, can you adjust it?
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google 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-51218) EMail-Ext does not send email, because or empty recipients
Title: Message Title
Zack Snyder edited a comment on JENKINS-51218
Re: EMail-Ext does not send email, because or empty recipients
[~markewaite]Okay, you can say I can get the email address of the user how changed the code with {{git log -n 1}}I am new to jenkins and do not understand how to do it properly.Can you please show me the complete code, see the pipeline script above how I send the email, can you adjust it?
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google 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-51218) EMail-Ext does not send email, because or empty recipients
Title: Message Title Zack Snyder commented on JENKINS-51218 Re: EMail-Ext does not send email, because or empty recipients Mark Waite Okay, you can say I can get the email address of the user how changed the code with git log -n 1 I am new to jenkins and do not understand how to do it properly. Can you please show me the complete code, see the pipeline script above how I send the email, can you adjust it? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51221) Email-Ext groovy.template does show wrong changes
Title: Message Title Zack Snyder commented on JENKINS-51221 Re: Email-Ext groovy.template does show wrong changes Mark Waite You are right, when you perform the second build, you will get the mail with the wrong list of changes That you get no email for the first build was the other bug: JENKINS-51218 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51221) Email-Ext groovy.template does show wrong changes
Title: Message Title Zack Snyder commented on JENKINS-51221 Re: Email-Ext groovy.template does show wrong changes Use jenkins, 2.107.2 and all the plugins I logged in the text file. Use the groocy HTML mail template for ext-mail. Create a repo and from this create a fork via bitbucket. Connect to bitbucket from jenkins via post webhook. Create a new branch and change something, push changes to origin and you will get the result I got. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51218) EMail-Ext does not send email, because or empty recipients
Title: Message Title Zack Snyder commented on JENKINS-51218 Re: EMail-Ext does not send email, because or empty recipients Mark Waite Okay, but how can I get what I want? When I make a new branch, push this new branch to origin a new build is triggered (code was changed, a commit is associated with my email address) How can the user gets notified that the build was successful? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51218) EMail-Ext does not send email, because or empty recipients
Title: Message Title Zack Snyder edited a comment on JENKINS-51218 Re: EMail-Ext does not send email, because or empty recipients !jenkins_changes.jpg|thumbnail! You are right, the git change log looks like its missing the important details...strange. [~davidvanlaatum]Can you please reopen and change the assignee? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51218) EMail-Ext does not send email, because or empty recipients
Title: Message Title Zack Snyder updated an issue Jenkins / JENKINS-51218 EMail-Ext does not send email, because or empty recipients Change By: Zack Snyder Attachment: jenkins_changes.jpg Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51218) EMail-Ext does not send email, because or empty recipients
Title: Message Title Zack Snyder commented on JENKINS-51218 Re: EMail-Ext does not send email, because or empty recipients You are right, the git change log looks like its missing the important details...strange. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51218) EMail-Ext does not send email, because or empty recipients
Title: Message Title Zack Snyder updated an issue Jenkins / JENKINS-51218 EMail-Ext does not send email, because or empty recipients Change By: Zack Snyder Component/s: git-plugin Component/s: scm-api-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51221) Email-Ext groovy.template does show wrong changes
Title: Message Title Zack Snyder edited a comment on JENKINS-51221 Re: Email-Ext groovy.template does show wrong changes See the attached git log: !git_log.jpg|thumbnail! It seems to be a bug in git SCM...PS: Can you change the component assignee to this plugin the correct developer ? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51221) Email-Ext groovy.template does show wrong changes
Title: Message Title Zack Snyder edited a comment on JENKINS-51221 Re: Email-Ext groovy.template does show wrong changes See the attached git log: !git_log.jpg|thumbnail! It seems to be a bug in git SCM... PS: Can you change the component to this plugin? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51221) Email-Ext groovy.template does show wrong changes
Title: Message Title Zack Snyder updated an issue Jenkins / JENKINS-51221 Email-Ext groovy.template does show wrong changes Change By: Zack Snyder Component/s: git-plugin Component/s: scm-api-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51221) Email-Ext groovy.template does show wrong changes
Title: Message Title Zack Snyder commented on JENKINS-51221 Re: Email-Ext groovy.template does show wrong changes See the attached git log: It seems to be a bug in git SCM... Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51221) Email-Ext groovy.template does show wrong changes
Title: Message Title Zack Snyder updated an issue Jenkins / JENKINS-51221 Email-Ext groovy.template does show wrong changes Change By: Zack Snyder Attachment: git_log.jpg Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51218) EMail-Ext does not send email, because or empty recipients
Title: Message Title Zack Snyder commented on JENKINS-51218 Re: EMail-Ext does not send email, because or empty recipients But it has the info who has committed the changes. So how can it be fixed? How can I get the developer of the current commit which is been building? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51221) Email-Ext groovy.template does show wrong changes
Title: Message Title Zack Snyder commented on JENKINS-51221 Re: Email-Ext groovy.template does show wrong changes Okay, maybe the API has changed and you have to use something different? Is there something I can do to fix it? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51221) Email-Ext groovy.template does show wrong changes
Title: Message Title Zack Snyder updated an issue Jenkins / JENKINS-51221 Email-Ext groovy.template does show wrong changes Change By: Zack Snyder I use the groovy template from email-ext in a multibranch pipeline (blue ocean).However, for unknown reason the email contains in the changed filed section hundreds of files, which where not touched in the commit (they are all from the 3rdpart directory in the src repo) but totally unrelated to any changes.!email-ext-changes.jpg|thumbnail! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51221) Email-Ext groovy.template does show wrong changes
Title: Message Title Zack Snyder created an issue Jenkins / JENKINS-51221 Email-Ext groovy.template does show wrong changes Issue Type: Bug Assignee: David van Laatum Attachments: email-ext-changes.jpg, installed_plugins.txt, my-html.template Components: email-ext-plugin Created: 2018-05-09 12:26 Environment: master node ubunut x64 slave node windows10 x64 Priority: Major Reporter: Zack Snyder I use the groovy template from email-ext in a multibranch pipeline (blue ocean). However, for unknown reason the email contains in the changed filed hundreds of files, which where not touched in the commit (they are all from the 3rdpart directory in the src repo) Add Comment
[JIRA] (JENKINS-51218) EMail-Ext does not send email, because or empty recipients
Title: Message Title
Zack Snyder created an issue
Jenkins / JENKINS-51218
EMail-Ext does not send email, because or empty recipients
Issue Type:
Bug
Assignee:
David van Laatum
Attachments:
installed_plugins.txt
Components:
email-ext-plugin
Created:
2018-05-09 12:12
Environment:
master node on Ubuntu x64 slave node on Windows
Priority:
Critical
Reporter:
Zack Snyder
I send my mail via groovy script in a multibranch-pipeline (blue ocean)
script
{
def currResult = getResultAsString(currentBuild)
def prevResult = getResultAsString(currentBuild.getPreviousBuild())
if (currResult != "SUCCESS" || prevResult != "SUCCESS")
{
echo 'send mail'
emailext body: '''${SCRIPT, template="my-html.template"}''',
recipientProviders: [[$class: 'DevelopersRecipientProvider'],
[$class: 'CulpritsRecipientProvider'],
[$class: 'UpstreamComitterRecipientProvider'],
],
subject: '[Jenkins]: ${JOB_NAME} ${BUILD_DISPLAY_NAME} - ' + currResult,
mimeType: 'text/html'
}
}
def getResultAsString(build)
{
def result =
[JIRA] (JENKINS-33900) save/apply button is missing when editing mutibranch jobs created inside a github organization folder
Title: Message Title Zack Snyder commented on JENKINS-33900 Re: save/apply button is missing when editing mutibranch jobs created inside a github organization folder Jesse Glick How do I trigger (or configure) a nightly build (build every midnight) via blue ocean? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50638) windows agent via SSH - Slave JVM has terminated. Exit code
Title: Message Title Zack Snyder commented on JENKINS-50638 Re: windows agent via SSH - Slave JVM has terminated. Exit code Ivan Fernandez Calvo Any update? Or are you now at the end of you knowledge? A tricky problem. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50868) Cannot checkout code via SHH when using blue ocean
Title: Message Title Zack Snyder commented on JENKINS-50868 Re: Cannot checkout code via SHH when using blue ocean When using checkout via SSH, I have to provide an username with key. Other option will work. However, I think the other credential option should not be available anyway. So in fact you can close it, or maybe see this as feature request to fix this. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50918) Bitbucket Source webhook endpoint fails: X-Event-Key HTTP header not found
Title: Message Title Zack Snyder commented on JENKINS-50918 Re: Bitbucket Source webhook endpoint fails: X-Event-Key HTTP header not found I can confirm this bug, I have the same result when entering the hook URL into the browser. Reported it here: JENKINS-47891 However, is this now a bug or can I just not enter the hook URL in a browser? Anyway, the hook will not trigger any build in jenkins. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-47891) Bitbucket branch source plugin does not understand the new Bitbucket webhooks
Title: Message Title
Zack Snyder edited a comment on JENKINS-47891
Re: Bitbucket branch source plugin does not understand the new Bitbucket webhooks
Any update here?I get the error, even using the plugin: https://marketplace.atlassian.com/plugins/nl.topicus.bitbucket.bitbucket-webhooks/server/overviewI use bitbucket 5.9.1 and jenkins 2.107.2{noformat} ava java .lang.Exception: X-Event-Key HTTP header not found at org.kohsuke.stapler.HttpResponses.error(HttpResponses.java:83) at com.cloudbees.jenkins.plugins.bitbucket.hooks.BitbucketSCMSourcePushHookReceiver.doNotify(BitbucketSCMSourcePushHookReceiver.java:94) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:374) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:841) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1650) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:225) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.auth.jwt.impl.JwtAuthenticationFilter.doFilter(JwtAuthenticationFilter.java:61) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1637) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:105) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1637) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at
[JIRA] (JENKINS-47891) Bitbucket branch source plugin does not understand the new Bitbucket webhooks
Title: Message Title Zack Snyder commented on JENKINS-47891 Re: Bitbucket branch source plugin does not understand the new Bitbucket webhooks Any update here? I get the error, even using the plugin: https://marketplace.atlassian.com/plugins/nl.topicus.bitbucket.bitbucket-webhooks/server/overview I use bitbucket 5.9.1 and jenkins 2.107.2 ava.lang.Exception: X-Event-Key HTTP header not found at org.kohsuke.stapler.HttpResponses.error(HttpResponses.java:83) at com.cloudbees.jenkins.plugins.bitbucket.hooks.BitbucketSCMSourcePushHookReceiver.doNotify(BitbucketSCMSourcePushHookReceiver.java:94) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:374) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:841) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1650) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:225) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.auth.jwt.impl.JwtAuthenticationFilter.doFilter(JwtAuthenticationFilter.java:61) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1637) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:105) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1637) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at
[JIRA] (JENKINS-50638) windows agent via SSH - Slave JVM has terminated. Exit code
Title: Message Title Zack Snyder commented on JENKINS-50638 Re: windows agent via SSH - Slave JVM has terminated. Exit code Here is the output: prefix_output.txt I just inserted text into the prefix field. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50638) windows agent via SSH - Slave JVM has terminated. Exit code
Title: Message Title Zack Snyder updated an issue Jenkins / JENKINS-50638 windows agent via SSH - Slave JVM has terminated. Exit code Change By: Zack Snyder Attachment: prefix_output.txt Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50676) Jenkins does not recognize "Jenkinsfile"
Title: Message Title Zack Snyder commented on JENKINS-50676 Re: Jenkins does not recognize "Jenkinsfile" What steps do you want me to write down? I setup jenkins in a clean environment. So the bug can be easily reproduced. Have one master on linux and one slave on windows. Add a repository, without jenkinsfile. Disable master agent. Then add the jenkinsfile to the repository. No jenkinsfile will be found. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50868) Cannot checkout code via SHH when using blue ocean
Title: Message Title Zack Snyder updated an issue Jenkins / JENKINS-50868 Cannot checkout code via SHH when using blue ocean Change By: Zack Snyder Summary: Cannot checkout code via SHH when using blue ocean Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50868) Cannot checkout code via SHH when using
Title: Message Title Zack Snyder created an issue Jenkins / JENKINS-50868 Cannot checkout code via SHH when using Issue Type: Bug Assignee: Unassigned Attachments: config.xml.zip, jenkins_ssh_credentials.jpg, Screenshot-2018-4-18 divas Config [Jenkins].png Components: blueocean-plugin Created: 2018-04-18 16:32 Environment: Windows10x64 slave agent Ubuntu 16.04x64 master agent Priority: Blocker Reporter: Zack Snyder I use blue ocean to configure and run my build. However, when I switch to checkout over SHH, it will not take the setting and will still checkout via HTTP: > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://bitbucket.SomeCompany.local/scm/~SomeUser/divas.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 No valid HEAD. Skipping the resetting > git clean -fdx # timeout=10 Fetching without tags Fetching upstream changes from http://bitbucket.SomeCompany.local/scm/~SomeUser/divas.git > git --version # timeout=10 > git fetch --no-tags --progress http://bitbucket.SomeCompany.local/scm/~SomeUser/divas.git +refs/heads/add-jenkins-file:refs/remotes/origin/add-jenkins-file ERROR: Error fetching remote repo 'origin' hudson.plugins.git.GitException: Failed to fetch from http://bitbucket.SomeCompany.local/scm/~SomeUser/divas.git at
[JIRA] (JENKINS-50638) windows agent via SSH - Slave JVM has terminated. Exit code
Title: Message Title Zack Snyder commented on JENKINS-50638 Re: windows agent via SSH - Slave JVM has terminated. Exit code Do you not find it strange, that I could execute the slave.jar file only when I was in the folder? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50638) windows agent via SSH - Slave JVM has terminated. Exit code
Title: Message Title Zack Snyder commented on JENKINS-50638 Re: windows agent via SSH - Slave JVM has terminated. Exit code You mean like this? [04/18/18 18:15:35] [SSH] Starting slave process: cd "/cygdrive/d/CI/jenkins-ssh" && java -Djava.util.logging.config.file=/cygdrive/d/CI/jenkins-ssh/logging.properties -jar slave.jar && echo "OK - retcode $?" <===[JENKINS REMOTING CAPACITY]===>Slave JVM has terminated. Exit code=0 [04/18/18 18:15:35] Launch failed - cleaning up connection [04/18/18 18:15:35] [SSH] Connection closed. I executed the previous command before, nothing. The agent has 16 GB of RAM I can also successfully build on the machine, when I use the connection of "Launch agent via web start". Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50676) Jenkins does not recognize "Jenkinsfile"
Title: Message Title Zack Snyder commented on JENKINS-50676 Re: Jenkins does not recognize "Jenkinsfile" The problem was happening, because I disable the master agent (where jenkins) is running. It was for me unclear, that I cannot disable this agent, otherwise not build will be performed. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50638) windows agent via SSH - Slave JVM has terminated. Exit code
Title: Message Title
Zack Snyder edited a comment on JENKINS-50638
Re: windows agent via SSH - Slave JVM has terminated. Exit code
Here is my output of the console (logged in from the master agent, where jenkins is running) :{noformat}BuildUser@W10x64-BuildSrv /cygdrive/c/Users/BuildUser$ D:bash: D:: command not foundBuildUser@W10x64-BuildSrv /cygdrive/c/Users/BuildUser$ cd d:BuildUser@W10x64-BuildSrv /cygdrive/d$ cd CI/jenkins-ssh/BuildUser@W10x64-BuildSrv /cygdrive/d/CI/jenkins-ssh$ d:bash: d:: command not foundBuildUser@W10x64-BuildSrv /cygdrive/d/CI/jenkins-ssh$ cd ..BuildUser@W10x64-BuildSrv /cygdrive/d/CI$ cd ..BuildUser@W10x64-BuildSrv /cygdrive/d$ cd C:BuildUser@W10x64-BuildSrv /cygdrive/c$ clsbash: cls: command not foundBuildUser@W10x64-BuildSrv /cygdrive/c$ clearbash: clear: command not foundBuildUser@W10x64-BuildSrv /cygdrive/c$ clsbash: cls: command not foundBuildUser@W10x64-BuildSrv /cygdrive/c$ "D:\CI\jenkins-ssh" && java -jar slave.jar -slaveLog=D:\CI\jenkins-ssh\log.txt"> pwd> ls>BuildUser@W10x64-BuildSrv /cygdrive/c$ d:bash: d:: command not foundBuildUser@W10x64-BuildSrv /cygdrive/c$ cd D:BuildUser@W10x64-BuildSrv /cygdrive/d$ cd CI/jenkinsBuildUser@W10x64-BuildSrv /cygdrive/d/CI/jenkins$ java -jar slave.jar -slaveLog=D:\CI\jenkins-ssh\log.txt">BuildUser@W10x64-BuildSrv /cygdrive/d/CI/jenkins$ java -jar slave.jarWARNING: Are you running agent from an interactive console?If so, you are probably using it incorrectly.See https://wiki.jenkins.io/display/JENKINS/Launching+agent+from+console<===[JENKINS REMOTING CAPACITY]===>rO0ABXNyABpodWRzb24ucmVtb3RpbmcuQ2FwYWJpbGl0eQABAgABSgAEbWFza3hwAP4={noformat} Only when I execute java.jar directly, (like you can see on the last cmd) I could start the agent, otherwise it was not returning from execution.See attached now the correct config.xml
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50638) windows agent via SSH - Slave JVM has terminated. Exit code
Title: Message Title Zack Snyder updated an issue Jenkins / JENKINS-50638 windows agent via SSH - Slave JVM has terminated. Exit code Change By: Zack Snyder Attachment: config.xml..zip Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50638) windows agent via SSH - Slave JVM has terminated. Exit code
Title: Message Title Zack Snyder updated an issue Jenkins / JENKINS-50638 windows agent via SSH - Slave JVM has terminated. Exit code Change By: Zack Snyder Attachment: config.xml..zip Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50638) windows agent via SSH - Slave JVM has terminated. Exit code
Title: Message Title Zack Snyder updated an issue Jenkins / JENKINS-50638 windows agent via SSH - Slave JVM has terminated. Exit code Change By: Zack Snyder Attachment: config.xml.zip Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50638) windows agent via SSH - Slave JVM has terminated. Exit code
Title: Message Title Zack Snyder commented on JENKINS-50638 Re: windows agent via SSH - Slave JVM has terminated. Exit code Here is my output of the console: BuildUser@W10x64-BuildSrv /cygdrive/c/Users/BuildUser $ D: bash: D:: command not found BuildUser@W10x64-BuildSrv /cygdrive/c/Users/BuildUser $ cd d: BuildUser@W10x64-BuildSrv /cygdrive/d $ cd CI/jenkins-ssh/ BuildUser@W10x64-BuildSrv /cygdrive/d/CI/jenkins-ssh $ d: bash: d:: command not found BuildUser@W10x64-BuildSrv /cygdrive/d/CI/jenkins-ssh $ cd .. BuildUser@W10x64-BuildSrv /cygdrive/d/CI $ cd .. BuildUser@W10x64-BuildSrv /cygdrive/d $ cd C: BuildUser@W10x64-BuildSrv /cygdrive/c $ cls bash: cls: command not found BuildUser@W10x64-BuildSrv /cygdrive/c $ clear bash: clear: command not found BuildUser@W10x64-BuildSrv /cygdrive/c $ cls bash: cls: command not found BuildUser@W10x64-BuildSrv /cygdrive/c $ "D:\CI\jenkins-ssh" && java -jar slave.jar -slaveLog=D:\CI\jenkins-ssh\log.txt" > pwd > ls > BuildUser@W10x64-BuildSrv /cygdrive/c $ d: bash: d:: command not found BuildUser@W10x64-BuildSrv /cygdrive/c $ cd D: BuildUser@W10x64-BuildSrv /cygdrive/d $ cd CI/jenkins BuildUser@W10x64-BuildSrv /cygdrive/d/CI/jenkins $ java -jar slave.jar -slaveLog=D:\CI\jenkins-ssh\log.txt" > BuildUser@W10x64-BuildSrv /cygdrive/d/CI/jenkins $ java -jar slave.jar WARNING: Are you running agent from an interactive console? If so, you are probably using it incorrectly. See https://wiki.jenkins.io/display/JENKINS/Launching+agent+from+console <===[JENKINS REMOTING CAPACITY]===>rO0ABXNyABpodWRzb24ucmVtb3RpbmcuQ2FwYWJpbGl0eQABAgABSgAEbWFza3hwAP4= Only when I execute java.jar directly, (like you can see on the last cmd) I could start the agent, otherwise it was not returning from execution. See attached now the correct config.xml Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-50638) windows agent via SSH - Slave JVM has terminated. Exit code
Title: Message Title Zack Snyder updated an issue Jenkins / JENKINS-50638 windows agent via SSH - Slave JVM has terminated. Exit code Change By: Zack Snyder Attachment: config.zip Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50638) windows agent via SSH - Slave JVM has terminated. Exit code
Title: Message Title Zack Snyder edited a comment on JENKINS-50638 Re: windows agent via SSH - Slave JVM has terminated. Exit code No files were created.!image-2018-04-18-11-55- 42 31 -400.png!!image-2018-04-18-11-55- 31 42 -400.png! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50638) windows agent via SSH - Slave JVM has terminated. Exit code
Title: Message Title Zack Snyder commented on JENKINS-50638 Re: windows agent via SSH - Slave JVM has terminated. Exit code No files were created. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50638) windows agent via SSH - Slave JVM has terminated. Exit code
Title: Message Title Zack Snyder updated an issue Jenkins / JENKINS-50638 windows agent via SSH - Slave JVM has terminated. Exit code Change By: Zack Snyder Attachment: image-2018-04-18-11-55-31-400.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50638) windows agent via SSH - Slave JVM has terminated. Exit code
Title: Message Title Zack Snyder updated an issue Jenkins / JENKINS-50638 windows agent via SSH - Slave JVM has terminated. Exit code Change By: Zack Snyder Attachment: image-2018-04-18-11-55-42-400.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50638) windows agent via SSH - Slave JVM has terminated. Exit code
Title: Message Title Zack Snyder commented on JENKINS-50638 Re: windows agent via SSH - Slave JVM has terminated. Exit code When using cygwin as bash, I get also the environment variables printed: [04/17/18 17:58:59] [SSH] Opening SSH connection to windows-build-server:22. [04/17/18 17:58:59] [SSH] SSH host key matches key seen previously for this host. Connection will be allowed. [04/17/18 17:58:59] [SSH] Authentication successful. [04/17/18 17:58:59] [SSH] The remote user's environment is: ALLUSERSPROFILE='C:\ProgramData' APPDATA='C:\Users\BuildUser\AppData\Roaming' BASH=/usr/bin/bash BASHOPTS=cmdhist:complete_fullquote:extquote:force_fignore:hostcomplete:interactive_comments:progcomp:promptvars:sourcepath BASH_ALIASES=() BASH_ARGC=() BASH_ARGV=() BASH_CMDS=() BASH_EXECUTION_STRING=set BASH_LINENO=() BASH_SOURCE=() BASH_VERSINFO=([0]="4" [1]="4" [2]="12" [3]="3" [4]="release" [5]="x86_64-unknown-cygwin") BASH_VERSION='4.4.12(3)-release' COMMONPROGRAMFILES='C:\Program Files\Common Files' COMPUTERNAME=W10X64-BUILDSRV COMSPEC='C:\WINDOWS\system32\cmd.exe' CYG_SYS_BASHRC=1 CommonProgramW6432='C:\Program Files\Common Files' DIRSTACK=() DXSDK_DIR='C:\Program Files (x86)\Microsoft DirectX SDK (June 2010)\' EUID=197611 GROUPS=() HOME=/home/BuildUser HOMEDRIVE=C: HOMEPATH='\Users\BuildUser' HOSTNAME=W10x64-BuildSrv HOSTTYPE=x86_64 IFS=$' \t\n' LOCALAPPDATA='C:\Users\BuildUser\AppData\Local' MACHTYPE=x86_64-unknown-cygwin NUMBER_OF_PROCESSORS=4 OPTERR=1 OPTIND=1 OS=Windows_NT OSTYPE=cygwin _OneDrive_='C:\Users\BuildUser\OneDrive' PATH='/cygdrive/c/ProgramData/Oracle/Java/javapath:/cygdrive/c/WINDOWS/system32:/cygdrive/c/WINDOWS:/cygdrive/c/WINDOWS/System32/Wbem:/cygdrive/c/WINDOWS/System32/WindowsPowerShell/v1.0:/cygdrive/c/Program Files (x86)/Windows Kits/8.1/Windows Performance Toolkit:/cygdrive/c/Program Files/Microsoft SQL Server/110/Tools/Binn:/cygdrive/c/Program Files (x86)/Microsoft SDKs/TypeScript/1.0:/cygdrive/c/Program Files/Microsoft SQL Server/120/Tools/Binn:/cygdrive/c/Program Files/Git/cmd:/cygdrive/c/Program Files/SafeNet/Authentication/SAC/x64:/cygdrive/c/Program Files/SafeNet/Authentication/SAC/x32:/cygdrive/c/WINDOWS/SysWOW64/WindowsPowerShell/v1.0/Modules/TShell/TShell:/cygdrive/c/WINDOWS/system32/config/systemprofile/AppData/Local/Microsoft/WindowsApps:/cygdrive/c/Users/BuildUser/AppData/Local/Microsoft/WindowsApps' PATHEXT='.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC' PIPESTATUS=([0]="0") PPID=1 PROCESSOR_ARCHITECTURE=AMD64 PROCESSOR_IDENTIFIER='Intel64 Family 6 Model 60 Stepping 3, GenuineIntel' PROCESSOR_LEVEL=6 PROCESSOR_REVISION=3c03 PROGRAMFILES='C:\Program Files' PROMPT='builduser@W10X64-BUILDSRV $P$G' PS4='+ ' PSModulePath='C:\Program Files\WindowsPowerShell\Modules;C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules' PUBLIC='C:\Users\Public' PWD=/cygdrive/c/Users/BuildUser ProgramData='C:\ProgramData' ProgramW6432='C:\Program Files' SHELL=/bin/bash SHELLOPTS=braceexpand:hashall:interactive-comments SHLVL=1 SSH_CLIENT='192.168.115.188 59638 22' SSH_CONNECTION='192.168.115.188 59638 192.168.120.187 22' SYSTEMDRIVE=C: SYSTEMROOT='C:\WINDOWS' TEMP=/cygdrive/c/Users/BuildUser/AppData/Local/Temp TERM=cygwin TMP=/cygdrive/c/Users/BuildUser/AppData/Local/Temp UID=197611 USERDOMAIN=WORKGROUP USERNAME=builduser USERPROFILE='C:\Users\BuildUser' VS110COMNTOOLS='C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\Tools\' VS120COMNTOOLS='C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Tools\'
[JIRA] (JENKINS-50638) windows agent via SSH - Slave JVM has terminated. Exit code
Title: Message Title
Zack Snyder edited a comment on JENKINS-50638
Re: windows agent via SSH - Slave JVM has terminated. Exit code
{noformat}$ sshd --foosshd: unknown option -- -OpenSSH_7.3p1, OpenSSL 1.0.2j 26 Sep 2016usage: sshd [-46DdeiqTt] [-b bits] [-C connection_spec] [-c host_cert_file][-E log_file] [-f config_file] [-g login_grace_time][-h host_key_file] [-k key_gen_time] [-o option] [-p port][-u len]{noformat} There are no other files in the folder: D:\CI\jenkins-ssh, except the "slave.jar"When I try to download: [ http://jenkins/computer/windows-ssh/config.xml ] I get the attached XML (config . zip)
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google 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-50638) windows agent via SSH - Slave JVM has terminated. Exit code
Title: Message Title Zack Snyder updated an issue Jenkins / JENKINS-50638 windows agent via SSH - Slave JVM has terminated. Exit code Change By: Zack Snyder Attachment: config.zip Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50638) windows agent via SSH - Slave JVM has terminated. Exit code
Title: Message Title Zack Snyder commented on JENKINS-50638 Re: windows agent via SSH - Slave JVM has terminated. Exit code $ sshd --foo sshd: unknown option -- - OpenSSH_7.3p1, OpenSSL 1.0.2j 26 Sep 2016 usage: sshd [-46DdeiqTt] [-b bits] [-C connection_spec] [-c host_cert_file] [-E log_file] [-f config_file] [-g login_grace_time] [-h host_key_file] [-k key_gen_time] [-o option] [-p port] [-u len] There are no other files in the folder: D:\CI\jenkins-ssh, except the "slave.jar" When I try to download: http://jenkins/computer/windows-ssh/config.xml I get the attached XML. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50638) windows agent via SSH - Slave JVM has terminated. Exit code
Title: Message Title Zack Snyder commented on JENKINS-50638 Re: windows agent via SSH - Slave JVM has terminated. Exit code I update the java version on the windows agent: C:\Users\BuildUser>java -version java version "1.8.0_161" Java(TM) SE Runtime Environment (build 1.8.0_161-b12) Java HotSpot(TM) 64-Bit Server VM (build 25.161-b12, mixed mode) However, the error is still there. 04/17/18 14:39:54] [SSH] Opening SSH connection to 192.168.120.187:22. [04/17/18 14:39:54] [SSH] SSH host key matches key seen previously for this host. Connection will be allowed. [04/17/18 14:39:54] [SSH] Authentication successful. [04/17/18 14:39:54] [SSH] The remote user's environment is: [04/17/18 14:39:54] [SSH] Checking java version of java [04/17/18 14:39:54] [SSH] java -version returned 1.8.0_161. [04/17/18 14:39:54] [SSH] Starting sftp client. [04/17/18 14:39:54] [SSH] Copying latest slave.jar... [04/17/18 14:39:55] [SSH] Copied 762,466 bytes. Expanded the channel window size to 4MB [04/17/18 14:39:55] [SSH] Starting slave process: cd "D:\CI\jenkins-ssh" && java -jar slave.jar -slaveLog=D:\CI\jenkins-ssh\log.txt <===[JENKINS REMOTING CAPACITY]===>Slave JVM has terminated. Exit code=0 [04/17/18 14:39:55] Launch failed - cleaning up connection [04/17/18 14:39:55] [SSH] Connection closed. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50638) windows agent via SSH - Slave JVM has terminated. Exit code
Title: Message Title Zack Snyder commented on JENKINS-50638 Re: windows agent via SSH - Slave JVM has terminated. Exit code Oleg Nenashev Normally on bash based script, its only allowed to use forward slahses, however, I also tried with back slashes and with quotes and without. Nothing. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50638) windows agent via SSH - Slave JVM has terminated. Exit code
Title: Message Title Zack Snyder commented on JENKINS-50638 Re: windows agent via SSH - Slave JVM has terminated. Exit code I added the jenkins version in the description Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50638) windows agent via SSH - Slave JVM has terminated. Exit code
Title: Message Title
Zack Snyder updated an issue
Jenkins / JENKINS-50638
windows agent via SSH - Slave JVM has terminated. Exit code
Change By:
Zack Snyder
The jar file on the slave fails to start.I use *"Launch Slave Agents via SSH"*{noformat}[04/06/18 15:32:05] [SSH] Opening SSH connection to 192.168.120.187:22.[04/06/18 15:32:06] [SSH] SSH host key matches key seen previously for this host. Connection will be allowed.[04/06/18 15:32:06] [SSH] Authentication successful.[04/06/18 15:32:06] [SSH] The remote user's environment is:[04/06/18 15:32:06] [SSH] Checking java version of java[04/06/18 15:32:06] [SSH] java -version returned 1.8.0_161.[04/06/18 15:32:06] [SSH] Starting sftp client.[04/06/18 15:32:06] [SSH] Copying latest slave.jar...[04/06/18 15:32:06] [SSH] Copied 762,466 bytes.Expanded the channel window size to 4MB[04/06/18 15:32:06] [SSH] Starting slave process: cd "D:\CI\jenkins" && java -jar slave.jar<===[JENKINS REMOTING CAPACITY]===>Slave JVM has terminated. Exit code=0[04/06/18 15:32:06] Launch failed - cleaning up connection[04/06/18 15:32:06] [SSH] Connection closed.{noformat}I use *Manually trusted key Verification Strategy*Require manual verification of initinial connection is *OFF*On windows, I use cygwin as bash, and openSSH from microsoft.Java version master:{noformat}java version "1.8.0_144"Java(TM) SE Runtime Environment (build 1.8.0_144-b01)Java HotSpot(TM) 64-Bit Server VM (build 25.144-b01, mixed mode){noformat}Java version slave:{noformat}java version "1.8.0_161"Java(TM) SE Runtime Environment (build 1.8.0_161-b12)Java HotSpot(TM) Client VM (build 25.161-b12, mixed mode, sharing){noformat} The jenkins version is: Jenkins ver. 2.107.2
Add Comment
[JIRA] (JENKINS-50638) windows agent via SSH - Slave JVM has terminated. Exit code
Title: Message Title Zack Snyder commented on JENKINS-50638 Re: windows agent via SSH - Slave JVM has terminated. Exit code I tried adding as "Suffix Start Slave Command" following: -slaveLog "D:/CI/jenkins-ssh/log.txt" -slaveLog="D:/CI/jenkins-ssh/log.txt" -logFile "D:/CI/jenkins-ssh/log.txt" -logFile="D:/CI/jenkins-ssh/log.txt" > "D:/CI/jenkins-ssh/log.txt" 2>"D:/CI/jenkins-ssh/Errorlog.txt" However, not log was created. Remark the white space at the start. But the commands where used, I get following output from the agent: [04/12/18 12:03:02] [SSH] Starting slave process: cd "D:/CI/jenkins-ssh" && java -jar slave.jar -slaveLog="D:/CI/jenkins-ssh/log.txt" In my sshd.log file from my ssh server on windows (where I want to run the slave) I get following output: 5436 2018-04-12 11:43:08.739 WARNING: could not open __PROGRAMDATA__\\ssh/moduli (No such file or directory), using fixed modulus 5436 2018-04-12 11:43:08.989 Accepted password for BuildUser from 192.168.115.188 port 59704 ssh2 7648 2018-04-12 11:43:09.713 Received disconnect from 192.168.115.188 port 59704:11: Closed due to user request. 7648 2018-04-12 11:43:09.713 Disconnected from 192.168.115.188 port 59704 192.168.115.188 => jenkins master Add Comment This message was sent by
[JIRA] (JENKINS-50638) windows agent via SSH - Slave JVM has terminated. Exit code
Title: Message Title Zack Snyder commented on JENKINS-50638 Re: windows agent via SSH - Slave JVM has terminated. Exit code Devin Nusbaum Any update here? I cannot use jenkins because of this. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50601) SSH plugin cannot negotiate
Title: Message Title Zack Snyder commented on JENKINS-50601 Re: SSH plugin cannot negotiate Devin Nusbaum Any update here? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50676) Jenkins does not recognize "Jenkinsfile"
Title: Message Title Zack Snyder commented on JENKINS-50676 Re: Jenkins does not recognize "Jenkinsfile" Maybe I cannot access the repository? Is there a way to test this? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50676) Jenkins does not recognize "Jenkinsfile"
Title: Message Title
Zack Snyder updated an issue
Jenkins / JENKINS-50676
Jenkins does not recognize "Jenkinsfile"
Change By:
Zack Snyder
After setting up my master jenkins on linux and a slave agent on windows.I want to use blue ocean to setup my jenkinsfile and perform my builds.However, although I have a {{Jenkinsfile}} in my repository, it will not be recognized.I get following message:{noformat}You don't have any branches that contain a JenkinsfileA Jenkinsfile is defined in your repository and describes how your pipeline will work.{noformat}Here my Jenkinsfile{noformat}pipeline { agent any stages {stage('Cmake configure') { steps {echo 'Hello World' }} }}{noformat}What can I do to fix this?I am connected to a local bitbucket server.I followed this tutorial here: https://jenkins.io/doc/book/blueocean/getting-started/What I found strange, that I do not need to setup a webhook in bitbucket or exchange any ssh keys. At least nothing is mentioned in the tutorial.The connection is made via: {{JNLP agent}} on windows. It is a multibranch pipeline.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50676) Jenkins does not recognize "Jenkinsfile"
Title: Message Title Zack Snyder updated an issue Jenkins / JENKINS-50676 Jenkins does not recognize "Jenkinsfile" Change By: Zack Snyder Attachment: system_info_jenkins.txt Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50676) Jenkins does not recognize "Jenkinsfile"
Title: Message Title Zack Snyder updated an issue Jenkins / JENKINS-50676 Jenkins does not recognize "Jenkinsfile" Change By: Zack Snyder Summary: Jenkins does not recognize scan "Jenkinsfile" Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50676) Jenkins does recognize scan "Jenkinsfile"
Title: Message Title
Zack Snyder created an issue
Jenkins / JENKINS-50676
Jenkins does recognize scan "Jenkinsfile"
Issue Type:
Bug
Assignee:
Unassigned
Components:
blueocean-plugin
Created:
2018-04-09 14:46
Environment:
windows-slave, linux-master
Priority:
Blocker
Reporter:
Zack Snyder
After setting up my master jenkins on linux and a slave agent on windows. I want to use blue ocean to setup my jenkinsfile and perform my builds. However, although I have a Jenkinsfile in my repository, it will not be recognized. I get following message:
You don't have any branches that contain a Jenkinsfile
A Jenkinsfile is defined in your repository and describes how your pipeline will work.
Here my Jenkinsfile
pipeline {
agent any
stages {
stage('Cmake configure') {
steps {
echo 'Hello World'
}
}
}
}
What can I do to fix this? I am connected to a local bitbucket server. I followed this tutorial here: https://jenkins.io/doc/book/blueocean/getting-started/ What I found strange, that I do not need to setup a webhook in bitbucket or exchange any ssh keys. At least nothing is mentioned in the tutorial. The connection is made via: JNLP agent on windows.
[JIRA] (JENKINS-50638) windows agent via SSH - Slave JVM has terminated. Exit code
Title: Message Title Zack Snyder updated an issue Jenkins / JENKINS-50638 windows agent via SSH - Slave JVM has terminated. Exit code Change By: Zack Snyder Summary: windows agent via SSH - Slave JVM has terminated. Exit code Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50638) windows agent via SSH
Title: Message Title Zack Snyder created an issue Jenkins / JENKINS-50638 windows agent via SSH Issue Type: Bug Assignee: Devin Nusbaum Attachments: system_info_jenkins.txt Components: ssh-agent-plugin, ssh-credentials-plugin, ssh-plugin, ssh-slaves-plugin Created: 2018-04-06 15:39 Environment: ubunut x64 as master win10x64 as slave Priority: Major Reporter: Zack Snyder The jar file on the slave fails to start. I use "Launch Slave Agents via SSH" [04/06/18 15:32:05] [SSH] Opening SSH connection to 192.168.120.187:22. [04/06/18 15:32:06] [SSH] SSH host key matches key seen previously for this host. Connection will be allowed. [04/06/18 15:32:06] [SSH] Authentication successful. [04/06/18 15:32:06] [SSH] The remote user's environment is: [04/06/18 15:32:06] [SSH] Checking java version of java [04/06/18 15:32:06] [SSH] java -version returned 1.8.0_161. [04/06/18 15:32:06] [SSH] Starting sftp client. [04/06/18 15:32:06] [SSH] Copying latest slave.jar... [04/06/18 15:32:06] [SSH] Copied 762,466 bytes. Expanded the channel window size to 4MB [04/06/18 15:32:06] [SSH] Starting slave process: cd "D:\CI\jenkins" && java -jar slave.jar <===[JENKINS REMOTING CAPACITY]===>Slave JVM has terminated. Exit code=0 [04/06/18 15:32:06] Launch failed - cleaning up connection [04/06/18 15:32:06] [SSH] Connection closed.
[JIRA] (JENKINS-50601) SSH plugin cannot negotiate
Title: Message Title Zack Snyder commented on JENKINS-50601 Re: SSH plugin cannot negotiate Like I already said, connection via bash works without a problem. The problem is the ssh jenkins plugin which is outdated. It seems to ship with an own openssh agent , which is of course wrong. It should always use the native one. (but I am not sure about that, maybe it invokes it wrong). Anyway, the problem is the jenkins plugin. I have the latest version of jenks. See the system_info. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50601) SSH plugin cannot negotiate
Title: Message Title
Zack Snyder updated an issue
Jenkins / JENKINS-50601
SSH plugin cannot negotiate
Change By:
Zack Snyder
I get following error (from sshd-log on windows) when trying to connect to my windows slave agent with openSSH running:{noformat}1716 18:01:04:153 Unable to negotiate with 192.168.115.188 port 56216: no matching key exchange method found. Their offer: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 {noformat} Connecting natively, via bash, works without a problem.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google 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-50601) SSH plugin cannot negotiate
Title: Message Title Zack Snyder created an issue Jenkins / JENKINS-50601 SSH plugin cannot negotiate Issue Type: Bug Assignee: Devin Nusbaum Attachments: system_info_jenkins.txt Components: ssh-agent-plugin, ssh-credentials-plugin, ssh-slaves-plugin Created: 2018-04-05 16:40 Environment: ubuntu x64 server 16.04 Jenkins ver. 2.107.1 ssh slave plugin 1.26 SSH credentials plugin 1.13 Priority: Major Reporter: Zack Snyder I get following error (from sshd-log on windows) when trying to connect to my windows slave agent with openSSH running: 1716 18:01:04:153 Unable to negotiate with 192.168.115.188 port 56216: no matching key exchange method found. Their offer: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
