Using params.item in agent docker section ...

[Eric Tan]

Hi

Is there a way to use parameters in the agent docker section like:

pipeline {

parameters {

string(name: 'OS_PORT', defaultValue: '')

string(name: 'CONTAINER_PORT', defaultValue: '')

   }

   agent { 

docker {

image 'someimage'

// args '-p :'

args '-p ${params.OS_PORT}:${params.CONTAINER_PORT}'

}

}


}


It does not work above.

Thanks

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/5c63e393-3da6-49a4-ad99-7e9814bbe828%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Mixing declarative and scripted pipeline syntax in one Jenkinsfile ...

[Eric Tan]

Thanks Daniel and Ishan!

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/ba8c7abc-f098-4912-bd8b-e1287c710de7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

JClouds with EC2 ignoring specified subnets?

[Andrew Grimberg]

Greetings folks,

I'm trying to get the JClouds plugin to bring up instances on EC2 under
a different VPC than the default. I've got a specific security group
configured attached to the correct VPC and the when the instance is
being brought up it tries to use that, however no matter what I do,
specify vpc or subnet in the subnets option it _always_ tries to bring
the instance up in the default vpc which then fails since the SG is not
part of that vpc.

Is there a reason why it's always trying to use the default vpc? Is
there any way that I can force it to only allocate against a particular
VPC? Is this a bug that I should be raising instead?

-Andy-

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/250a8df6-15cb-dfe9-e7f0-bf2380ffc5eb%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: Z/OS Connector; return results to Jenkins from a secondary job

[rsjrny]

follow the instructions 
at: https://wiki.jenkins.io/display/JENKINS/IBM+zOS+Connector

in the source manager you can select None if you do not want to interface  
with the source manager

On Wednesday, April 5, 2017 at 9:50:34 AM UTC-4, Patricio Iglesias wrote:
>
> Im trying to invoke a JCL with no luck. Could you (or anyone) kindly post 
> your job configuration as an example please?
>
> El jueves, 21 de julio de 2016, 14:40:22 (UTC+2), rsjrny escribió:
>>
>> I am able to successful use the Z/OS connector to submit my build job and 
>> return it's results but unfortunately the result are not the results I 
>> need. The results are only from the single job submitted by Jenkins
>>
>> My process submits JCL that in turn submits 1-nn other JCL jobs to 
>> execute a build of 1-nn modules.Each of these 1-nn jobs run to completion 
>> and the Return Code of the 1-nn jobs are the real completion I need 
>> reported in Jenkins
>>
>>
>> What I need to return to jenkins is the log from all the modules 
>> generated after job nn has completed.
>>
>> The process looks like this:
>>
>>1. Submit Main Job using jenkins which in turn submits individual 
>>element generates
>>   1. Submits 1-nn element generate 
>>   2. Log results from element generate
>>   3. repeat until all jobs have finished
>>2. Return  complete Log result to Jenkins with MAXCC
>>
>>
>>
>> All suggestions are welcome
>>
>> thanks,
>>
>> Russ
>>
>>
>> 
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/48ab8dc9-a139-4703-a3b7-4738f7320c36%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Trying to use CopyArtifact in declarative pipeline

[dandeliondodgeball]

Ok, finally got it.  This worked.

script {
step ([$class: 'CopyArtifact', projectName: 
'Create_Infrastructure_archive']);
}

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/01208ee3-91b2-4520-84cb-54a9823a56ef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: “Copy artifacts from another project” and Jenkinsfiles are exclusive, correct?

[dandeliondodgeball]

Moved this to new 
post https://groups.google.com/forum/#!topic/jenkinsci-users/OU8Kzl6CJXk

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/c8a8e8b4-4763-4bee-a311-c4a77d3a3f3c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Trying to use CopyArtifact in declarative pipeline

[dandeliondodgeball]

Original 
post: https://groups.google.com/forum/#!topic/jenkinsci-users/n1oqnnW1A98

So this worked (scripted)


node {
step ([$class: 'CopyArtifact', projectName: 
'Create_Infrastructure_archive']);



This doesn't break, but nothing happens (declarative).  

pipeline {
agent any
stages {
stage('Build') {
steps {
script {
[$class: 'CopyArtifact', projectName: 
'Create_Infrastructure_archive']
}

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/3ad1872f-7e22-478a-b807-74e16c58378d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Failed to connect to http://jenkins.build-env.svc.cluster.local:8080/tcpSlaveAgentListener/: jenkins.build-env.svc.cluster.local

[Carlos Sanchez]

you are correct your kubernetes DNS can't resolve the name, assuming you
have a service jenkins in the build-env namespace

On Thu, Oct 5, 2017 at 4:09 PM, WANG, YAN-HONG 
wrote:

> Hello,
>
> My environment:
> Jenkins: 2.73.1
> Jenkins plugin (kubernetes: *1.0*).
> Kuberntes Server: *v1.7.7* ( One master and one minion)
> Platform: Ubuntu 16.04 (in *Synnefo *cluster environment)
>
> When I execute pipeline job with kubernetes plugin in Jenkins environment.
>
> The slave-jksnf-q6dlr is stay in "offline" state.
>
> *$ ​kubectl --namespace=build-env logs slave-jksnf-q6dlr jnlp*
> Warning: JnlpProtocol3 is disabled by default, use JNLP_PROTOCOL_OPTS to
> alter the behavior
> Warning: SECRET is defined twice in command-line arguments and the
> environment variable
> Warning: AGENT_NAME is defined twice in command-line arguments and the
> environment variable
> Oct 05, 2017 1:29:32 PM hudson.remoting.jnlp.Main createEngine
> INFO: Setting up slave: slave-jksnf-q6dlr
> Oct 05, 2017 1:29:32 PM hudson.remoting.jnlp.Main$CuiListener 
> INFO: Jenkins agent is running in headless mode.
> Oct 05, 2017 1:29:32 PM hudson.remoting.Engine startEngine
> WARNING: No Working Directory. Using the legacy JAR Cache location:
> /home/jenkins/.jenkins/cache/jars
> Oct 05, 2017 1:29:32 PM hudson.remoting.jnlp.Main$CuiListener status
> INFO: Locating server among [http://jenkins.build-env.svc.
> cluster.local:8080/]
> Oct 05, 2017 1:29:37 PM hudson.remoting.jnlp.Main$CuiListener error
> SEVERE: Failed to connect to http://jenkins.build-env.svc.
> cluster.local:8080/tcpSlaveAgentListener/: jenkins.build-env.svc.cluster.
> local
> java.io.IOException: Failed to connect to http://jenkins.build-env.svc.
> cluster.local:8080/tcpSlaveAgentListener/: jenkins.build-env.svc.cluster.
> local
> at org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(
> JnlpAgentEndpointResolver.java:161)
> at hudson.remoting.Engine.innerRun(Engine.java:495)
> at hudson.remoting.Engine.run(Engine.java:447)
> Caused by: java.net.UnknownHostException: jenkins.build-env.svc.cluster.
> local
> at java.net.AbstractPlainSocketImpl.connect(
> AbstractPlainSocketImpl.java:184)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> at java.net.Socket.connect(Socket.java:589)
> at sun.net.NetworkClient.doConnect(NetworkClient.java:175)
> at sun.net.www.http.HttpClient.openServer(HttpClient.java:463)
> at sun.net.www.http.HttpClient.openServer(HttpClient.java:558)
> at sun.net.www.http.HttpClient.(HttpClient.java:242)
> at sun.net.www.http.HttpClient.New(HttpClient.java:339)
> at sun.net.www.http.HttpClient.New(HttpClient.java:357)
> at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(
> HttpURLConnection.java:1202)
> at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(
> HttpURLConnection.java:1138)
> at sun.net.www.protocol.http.HttpURLConnection.plainConnect(
> HttpURLConnection.java:1032)
> at sun.net.www.protocol.http.HttpURLConnection.connect(
> HttpURLConnection.java:966)
> at org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(
> JnlpAgentEndpointResolver.java:158)
> ... 2 more
>
> It looks seem DNS can't solve name issue? or?
> But, in minikube environment, there is no this problem...
>
> Thanks very much.
>
> Hong
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-users/CADLWyO2XJG-50ouKNe7yVm6BiQ_-
> cYoxQQrWg7P2iRRX7FZ%3DAA%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CALHFn6MzS_EW_Fn4CQYb%2BRhi4xk7C7kuJ%2BBV-HjD%2Byp8b%3DaTvw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: How alert users of failed tests when running Jenkins locally?

[Mark Waite]

I think you should choose a communication system that users already use,
and publish results to that communication system.  If those who need to be
notified are regular users of Slack (or HipChat or ...), connect those
Jenkins instances to the messaging app and send messages to the committer.
If they regularly read e-mail, send them an e-mail.  If they regularly read
text messages, send them a text.

If you're feeling really novel, you could buy each person a "blink" device
to plug into a USB port, then notify by changing the color or pattern of
the blink device.

Mark Waite

On Thu, Oct 5, 2017 at 8:32 AM Anna Freiholtz 
wrote:

> If you setup Jenkins on local machines running tests on commits in the
> local repository, how do you alert the users of failed tests?
>
> I don't want them to have to check Jenkins for themselves. I know when I
> am working I can get so into it I probably won't remember to check if my
> commit failed tests in Jenkins..
>
> /Anna
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/eaca2f46-fe0f-4118-829e-9599aee79906%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtHo0doVjooGLDvtDQKRNj%3D5LiaJSNZcS-vbXQ9%3DL%3DeAiQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: ERROR: Processing failed due to a bug in the code.

[Mark Waite]

That failure message is unrelated to git.

The message "java.lang.RuntimeException: java.lang.IllegalArgumentException:
No
matching Artifactory server was found in General Configuration. Please
update your job configuration." seems to indicate that some method which
expects an artifactory server to be defined globally is not finding a
globally defined artifactory server.  Check what changed in your global
configuration.

Mark Waite

On Thu, Oct 5, 2017 at 8:47 AM Charles Karney  wrote:

> I'm running Jenkins 1.589.
>
>
> On Thursday, October 5, 2017 at 10:32:20 AM UTC-4, Charles Karney wrote:
>>
>> Triggering a Jenkins build on a job that has "usually" worked gives:
>>
>>   ERROR: Processing failed due to a bug in the code. Please report this
>>   to jenkinsci-users@googlegroups.com
>>
>> The log up to this point is
>>
>>   Started by user Charles Karney
>>   [EnvInject] - Loading node environment variables.
>>   Building remotely on bso-centos7-gpu (centos7gpu slave) in workspace
>> /var/lib/jenkins/workspace/vt-geographiclib
>>
>>   Deleting project workspace... done
>>
>>   Cloning the remote Git repository
>>   Cloning repository ssh://
>> g...@scm-vt.sarnoff.com/common/geographiclib.git
>> 
>>> /usr/bin/git init
>> /var/lib/jenkins/workspace/vt-geographiclib/project # timeout=10
>>   Fetching upstream changes from
>> ssh://g...@scm-vt.sarnoff.com/common/geographiclib.git
>>> /usr/bin/git --version # timeout=10
>>> /usr/bin/git -c core.askpass=true fetch --tags --progress
>> ssh://g...@scm-vt.sarnoff.com/common/geographiclib.git
>> +refs/heads/*:refs/remotes/origin/*
>> 
>>> /usr/bin/git config remote.origin.url
>> ssh://g...@scm-vt.sarnoff.com/common/geographiclib.git # timeout=10
>>> /usr/bin/git config --add remote.origin.fetch
>> +refs/heads/*:refs/remotes/origin/* # timeout=10
>>> /usr/bin/git config remote.origin.url
>> ssh://g...@scm-vt.sarnoff.com/common/geographiclib.git # timeout=10
>>   Fetching upstream changes from
>> ssh://g...@scm-vt.sarnoff.com/common/geographiclib.git
>>> /usr/bin/git -c core.askpass=true fetch --tags --progress
>> ssh://g...@scm-vt.sarnoff.com/common/geographiclib.git
>> +refs/heads/*:refs/remotes/origin/*
>> 
>>> /usr/bin/git rev-parse refs/remotes/origin/feature/majic^{commit}
>> # timeout=10
>>> /usr/bin/git rev-parse
>> refs/remotes/origin/origin/feature/majic^{commit} # timeout=10
>>   Checking out Revision efd6519b02aa23c02af3c4f25064b9ea91ec09f0
>> (refs/remotes/origin/feature/majic)
>>> /usr/bin/git config core.sparsecheckout # timeout=10
>>> /usr/bin/git checkout -f efd6519b02aa23c02af3c4f25064b9ea91ec09f0
>>> /usr/bin/git rev-list f98d0f44741e37d12d849870df884c0cdbd24bc5 #
>> timeout=10
>>   ERROR: Processing failed due to a bug in the code. Please report
>> this to jenkinsci-users@googlegroups.com
>>   java.lang.RuntimeException: java.lang.IllegalArgumentException: No
>> matching Artifactory server was found in General Configuration. Please
>> update your job configuration.
>>   ...
>>
>> I can execute the git commands "manually" on my machine OK.  The last
>> command
>>
>>   /usr/bin/git rev-list f98d0f44741e37d12d849870df884c0cdbd24bc5
>>
>> returns a list of 166 commits.  Let me know if you want additional
>> information.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/7302f169-666b-49bf-8743-c75459343dac%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtHyGd2tD3SCLjyOijUmy30fXOxmEfLMyxUkxzU4n3jKBQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: ERROR: Processing failed due to a bug in the code.

[Charles Karney]

I'm running Jenkins 1.589.

On Thursday, October 5, 2017 at 10:32:20 AM UTC-4, Charles Karney wrote:
>
> Triggering a Jenkins build on a job that has "usually" worked gives: 
>
>   ERROR: Processing failed due to a bug in the code. Please report this 
>   to jenkinsci-users@googlegroups.com 
>
> The log up to this point is 
>
>   Started by user Charles Karney 
>   [EnvInject] - Loading node environment variables. 
>   Building remotely on bso-centos7-gpu (centos7gpu slave) in workspace 
> /var/lib/jenkins/workspace/vt-geographiclib 
>
>   Deleting project workspace... done 
>
>   Cloning the remote Git repository 
>   Cloning repository ssh://g...@scm-vt.sarnoff.com/common/geographiclib.git 
> 
>  
>> /usr/bin/git init 
> /var/lib/jenkins/workspace/vt-geographiclib/project # timeout=10 
>   Fetching upstream changes from 
> ssh://g...@scm-vt.sarnoff.com/common/geographiclib.git 
>> /usr/bin/git --version # timeout=10 
>> /usr/bin/git -c core.askpass=true fetch --tags --progress 
> ssh://g...@scm-vt.sarnoff.com/common/geographiclib.git 
> +refs/heads/*:refs/remotes/origin/* 
> 
>  
>> /usr/bin/git config remote.origin.url 
> ssh://g...@scm-vt.sarnoff.com/common/geographiclib.git # timeout=10 
>> /usr/bin/git config --add remote.origin.fetch 
> +refs/heads/*:refs/remotes/origin/* # timeout=10 
>> /usr/bin/git config remote.origin.url 
> ssh://g...@scm-vt.sarnoff.com/common/geographiclib.git # timeout=10 
>   Fetching upstream changes from 
> ssh://g...@scm-vt.sarnoff.com/common/geographiclib.git 
>> /usr/bin/git -c core.askpass=true fetch --tags --progress 
> ssh://g...@scm-vt.sarnoff.com/common/geographiclib.git 
> +refs/heads/*:refs/remotes/origin/* 
> 
>  
>> /usr/bin/git rev-parse refs/remotes/origin/feature/majic^{commit} 
> # timeout=10 
>> /usr/bin/git rev-parse 
> refs/remotes/origin/origin/feature/majic^{commit} # timeout=10 
>   Checking out Revision efd6519b02aa23c02af3c4f25064b9ea91ec09f0 
> (refs/remotes/origin/feature/majic) 
>> /usr/bin/git config core.sparsecheckout # timeout=10 
>> /usr/bin/git checkout -f efd6519b02aa23c02af3c4f25064b9ea91ec09f0 
>> /usr/bin/git rev-list f98d0f44741e37d12d849870df884c0cdbd24bc5 # 
> timeout=10 
>   ERROR: Processing failed due to a bug in the code. Please report 
> this to jenkinsci-users@googlegroups.com 
>   java.lang.RuntimeException: java.lang.IllegalArgumentException: No 
> matching Artifactory server was found in General Configuration. Please 
> update your job configuration. 
>   ... 
>
> I can execute the git commands "manually" on my machine OK.  The last 
> command 
>
>   /usr/bin/git rev-list f98d0f44741e37d12d849870df884c0cdbd24bc5 
>
> returns a list of 166 commits.  Let me know if you want additional 
> information. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/7302f169-666b-49bf-8743-c75459343dac%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

How alert users of failed tests when running Jenkins locally?

[Anna Freiholtz]

If you setup Jenkins on local machines running tests on commits in the 
local repository, how do you alert the users of failed tests?

I don't want them to have to check Jenkins for themselves. I know when I am 
working I can get so into it I probably won't remember to check if my 
commit failed tests in Jenkins..

/Anna

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/eaca2f46-fe0f-4118-829e-9599aee79906%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

ERROR: Processing failed due to a bug in the code.

[Charles Karney]

Triggering a Jenkins build on a job that has "usually" worked gives:

  ERROR: Processing failed due to a bug in the code. Please report this
  to jenkinsci-users@googlegroups.com

The log up to this point is

  Started by user Charles Karney
  [EnvInject] - Loading node environment variables.
  Building remotely on bso-centos7-gpu (centos7gpu slave) in workspace
/var/lib/jenkins/workspace/vt-geographiclib

  Deleting project workspace... done

  Cloning the remote Git repository
  Cloning repository ssh://g...@scm-vt.sarnoff.com/common/geographiclib.git
   > /usr/bin/git init
/var/lib/jenkins/workspace/vt-geographiclib/project # timeout=10
  Fetching upstream changes from
ssh://g...@scm-vt.sarnoff.com/common/geographiclib.git
   > /usr/bin/git --version # timeout=10
   > /usr/bin/git -c core.askpass=true fetch --tags --progress
ssh://g...@scm-vt.sarnoff.com/common/geographiclib.git
+refs/heads/*:refs/remotes/origin/*
   > /usr/bin/git config remote.origin.url
ssh://g...@scm-vt.sarnoff.com/common/geographiclib.git # timeout=10
   > /usr/bin/git config --add remote.origin.fetch
+refs/heads/*:refs/remotes/origin/* # timeout=10
   > /usr/bin/git config remote.origin.url
ssh://g...@scm-vt.sarnoff.com/common/geographiclib.git # timeout=10
  Fetching upstream changes from
ssh://g...@scm-vt.sarnoff.com/common/geographiclib.git
   > /usr/bin/git -c core.askpass=true fetch --tags --progress
ssh://g...@scm-vt.sarnoff.com/common/geographiclib.git
+refs/heads/*:refs/remotes/origin/*
   > /usr/bin/git rev-parse refs/remotes/origin/feature/majic^{commit}
# timeout=10
   > /usr/bin/git rev-parse
refs/remotes/origin/origin/feature/majic^{commit} # timeout=10
  Checking out Revision efd6519b02aa23c02af3c4f25064b9ea91ec09f0
(refs/remotes/origin/feature/majic)
   > /usr/bin/git config core.sparsecheckout # timeout=10
   > /usr/bin/git checkout -f efd6519b02aa23c02af3c4f25064b9ea91ec09f0
   > /usr/bin/git rev-list f98d0f44741e37d12d849870df884c0cdbd24bc5 # timeout=10
  ERROR: Processing failed due to a bug in the code. Please report
this to jenkinsci-users@googlegroups.com
  java.lang.RuntimeException: java.lang.IllegalArgumentException: No
matching Artifactory server was found in General Configuration. Please
update your job configuration.
  ...

I can execute the git commands "manually" on my machine OK.  The last
command

  /usr/bin/git rev-list f98d0f44741e37d12d849870df884c0cdbd24bc5

returns a list of 166 commits.  Let me know if you want additional
information.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAH36mb_QNu2%3DXH0dcb1-4SAKm5HhjnSZKWuRqQAawOCEQAgC1g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Failed to connect to http://jenkins.build-env.svc.cluster.local:8080/tcpSlaveAgentListener/: jenkins.build-env.svc.cluster.local

[WANG, YAN-HONG]

Hello,

My environment:
Jenkins: 2.73.1
Jenkins plugin (kubernetes: *1.0*).
Kuberntes Server: *v1.7.7* ( One master and one minion)
Platform: Ubuntu 16.04 (in *Synnefo *cluster environment)

When I execute pipeline job with kubernetes plugin in Jenkins environment.

The slave-jksnf-q6dlr is stay in "offline" state.

*$ ​kubectl --namespace=build-env logs slave-jksnf-q6dlr jnlp*
Warning: JnlpProtocol3 is disabled by default, use JNLP_PROTOCOL_OPTS to
alter the behavior
Warning: SECRET is defined twice in command-line arguments and the
environment variable
Warning: AGENT_NAME is defined twice in command-line arguments and the
environment variable
Oct 05, 2017 1:29:32 PM hudson.remoting.jnlp.Main createEngine
INFO: Setting up slave: slave-jksnf-q6dlr
Oct 05, 2017 1:29:32 PM hudson.remoting.jnlp.Main$CuiListener 
INFO: Jenkins agent is running in headless mode.
Oct 05, 2017 1:29:32 PM hudson.remoting.Engine startEngine
WARNING: No Working Directory. Using the legacy JAR Cache location:
/home/jenkins/.jenkins/cache/jars
Oct 05, 2017 1:29:32 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Locating server among [
http://jenkins.build-env.svc.cluster.local:8080/]
Oct 05, 2017 1:29:37 PM hudson.remoting.jnlp.Main$CuiListener error
SEVERE: Failed to connect to
http://jenkins.build-env.svc.cluster.local:8080/tcpSlaveAgentListener/:
jenkins.build-env.svc.cluster.local
java.io.IOException: Failed to connect to
http://jenkins.build-env.svc.cluster.local:8080/tcpSlaveAgentListener/:
jenkins.build-env.svc.cluster.local
at
org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:161)
at hudson.remoting.Engine.innerRun(Engine.java:495)
at hudson.remoting.Engine.run(Engine.java:447)
Caused by: java.net.UnknownHostException:
jenkins.build-env.svc.cluster.local
at
java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:184)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at sun.net.NetworkClient.doConnect(NetworkClient.java:175)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:463)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:558)
at sun.net.www.http.HttpClient.(HttpClient.java:242)
at sun.net.www.http.HttpClient.New(HttpClient.java:339)
at sun.net.www.http.HttpClient.New(HttpClient.java:357)
at
sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1202)
at
sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1138)
at
sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1032)
at
sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:966)
at
org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:158)
... 2 more

It looks seem DNS can't solve name issue? or?
But, in minikube environment, there is no this problem...

Thanks very much.

Hong

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CADLWyO2XJG-50ouKNe7yVm6BiQ_-cYoxQQrWg7P2iRRX7FZ%3DAA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Can Jenkins be configured to build and deploy Workday HCM integrations automatically.

[Prashanth Gopawar]

Can Jenkins be configured to build and deploy Workday HCM integrations 
automatically. Has anyone used Continuous integration and Continuous 
deployment model using Jenkins to build and deploy Workday HCM integrations 
or business processes automatically.

Please advise if anyone has already taken this approach or can throw some 
light on the subject.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/c70c96c5-d118-4ebe-852a-b50d7d537268%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Another CLI question

[Riccardo Foschia]

Am 04.10.2017 um 22:37 schrieb Richard Ginga:

Hi Michael, thanks for the response, nothing in my nginx configuration
indicates any buffering explicitly one way or the other.



Richard, just in case you are using any kind of anti-virus software on 
the machine executing the CLI commands, it's probably an issue with an 
anti-virus software (as in the other thread with CLI issues you didn't 
wan't to hijack ;-) ): try to disable the scanning of HTTP responses in 
your anti-virus software.



You should also try to enable logging in the CLI client like this:

java -jar jenkins-cli.jar -noKeyAuth -s 
https://stt-jenkins.disruptorbeam.com/ -logging FINE connect-node 




On Wed, Oct 4, 2017 at 3:17 PM, Michael Pailloncy <
michael.paillo...@gmail.com> wrote:


If you run this very same command directly on the Jenkins server and
without reaching it through your reverse proxy, does it work ?
I'm wondering if it's not related to the configuration of your reverse
proxy. As described in this documentation
, you
need to ensure that it doesn't buffer request/response bodies when serving
Jenkins through HTTPS.

Hopefully it helps.

2017-10-04 19:01 GMT+02:00 Richard Ginga :


is anybody out there?

my script syntax for this is

cmd = 'java -jar ~/Downloads/jenkins-cli.jar -noKeyAuth -s
https://stt-jenkins.disruptorbeam.com/ -auth
rginga:0793b086e3c9272ddeb0daff1093518c connect-node ' + params.NODENAME
st = sh(returnStatus: true, script: cmd)



On Wed, Oct 4, 2017 at 10:08 AM, Richard Ginga 
wrote:


I see a thread happening on CLI issues. I have a different
question/issue and do not want to hijack that other discussion.

when running any cli in a pipeline script I an getting below but the
command works

*00:04:11.368* + java -jar /Users/jenkins/Downloads/jenkins-cli.jar -noKeyAuth 
-s https://stt-jenkins.disruptorbeam.com/ -auth rginga:xx connect-node 
perf-test-client3

*00:04:28.597* Oct 04, 2017 9:52:34 AM hudson.cli.CLI$5 run*00:04:28.597* 
WARNING: null*00:04:28.597* java.io.IOException: Stream is closed*00:04:28.597* 
  at 
sun.net.www.protocol.http.HttpURLConnection$StreamingOutputStream.checkError(HttpURLConnection.java:3512)*00:04:28.597*
  at 
sun.net.www.protocol.http.HttpURLConnection$StreamingOutputStream.write(HttpURLConnection.java:3486)*00:04:28.597*
   at 
java.io.DataOutputStream.writeInt(DataOutputStream.java:197)*00:04:28.597*   at 
hudson.cli.PlainCLIProtocol$EitherSide.send(PlainCLIProtocol.java:175)*00:04:28.597*
 at 
hudson.cli.PlainCLIProtocol$ClientSide.sendEndStdin(PlainCLIProtocol.java:347)*00:04:28.597*
 at hudson.cli.CLI$5.run(CLI.java:679)*00:04:28.597*

--
Dick Ginga
Build Engineer
rgi...@disruptorbeam.com





--
Dick Ginga
Build Engineer
rgi...@disruptorbeam.com

--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/ms
gid/jenkinsci-users/CAL3PpaU2vJiaU65icq6vBNwBs%3D7_%3DvG_a4_
tOq_vdVxHbLo4Ug%40mail.gmail.com

.

For more options, visit https://groups.google.com/d/optout.



--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/jenkinsci-users/CAPO77c2yn_VvCtXNbeA9R27E2yNm8xb2_
PTn1UEK-0ocoTHvXw%40mail.gmail.com

.
For more options, visit https://groups.google.com/d/optout.







--

META-LEVEL Software AG
Lyonerring 1
66121 Saarbrücken
Deutschland
Tel: +49 - 681 / 99687-0
Fax: +49 - 681 / 99687-99
Mail: i...@meta-level.de
Web: www.meta-level.de

Rechtsform: Aktiengesellschaft
Sitz: Saarbrücken
HR B Nr. 13 380 Amtsgericht Saarbrücken
USt-IdNr. DE 1 38 17
Vorstände: Dipl.-Inform. Peter Badt und Dipl.-Inform. Peter Raber
Vorsitzender des Aufsichtsrats:  Reinhard Kuhn

--
You received this message because you are subscribed to the Google Groups "Jenkins 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/8db26ce9-fe13-c85e-6db6-5ac83724a6a8%40meta-level.de.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins CLI with http protocol does not respond in 2.81

[Riccardo Foschia]

After some research we found the problem: it was the anti-virus software 
because it damaged the HTTP responses.  After disabling the HTTP 
scanning feature everything worked fine.


Thanks to all for their help!

Am 04.10.2017 um 13:50 schrieb Riccardo Foschia:

Hi all,

after an upgrade of Jenkins 1.638 to 2.81 CLI I need to switch to http
protocol but it doesn't work (SSH protocol seems to work after the
upgrade).

No matter which CLI command I use, after a few seconds the call returns
but shows no result. E.g.

java -jar jenkins-cli.jar -s http://10.0.3.108 -logger FINE help

called from a Windows command line returns nothing. No errors are
reported. On console I see only the following output:

Okt 04, 2017 1:11:33 PM hudson.cli.CLI _main
FINE: using connection mode HTTP
Okt 04, 2017 1:11:33 PM hudson.cli.CLI plainHttpConnection
FINE: Trying to connect to http://10.0.3.108:8080/ via plain protocol
over HTTP
Okt 04, 2017 1:11:34 PM hudson.cli.FullDuplexHttpStream 
FINE: establishing download side
Okt 04, 2017 1:11:39 PM hudson.cli.FullDuplexHttpStream 
FINE: established download side
Okt 04, 2017 1:11:39 PM hudson.cli.FullDuplexHttpStream 
FINE: establishing upload side
Okt 04, 2017 1:11:39 PM hudson.cli.FullDuplexHttpStream 
FINE: established upload side


On Jenkins server (running on Debian) I enabled HTTP access log and I
see the following lines there:

10.0.1.66 - - [04/Okt/2017:13:41:50 +0200] "GET / HTTP/1.1" 200 295675
"-" "Java/1.8.0_141"
10.0.1.66 - - [04/Okt/2017:13:41:58 +0200] "POST /cli HTTP/1.1" 200 6458
"-" "Java/1.8.0_141"
10.0.1.66 - - [04/Okt/2017:13:41:58 +0200] "POST /cli HTTP/1.1" 200 0
"-" "Java/1.8.0_141"

I also tried this with other CLI commands like version or who-am-i and
providing an additional -auth parameter with the right API-Token to the
command line like

java -jar jenkins-cli.jar -s http://10.0.3.108 -auth foschia:
02a781f2a2fe96e8d38dc548ab07912e -logger FINE version

but the result on the command line and the log outputs on client and
server side remain the same.

After reading all available Jenkins documentation and googling around I
really do not know, what to do next.

I would really appreciate any hints.

Thanks in advance,
Riccardo



--

META-LEVEL Software AG
Lyonerring 1
66121 Saarbrücken
Deutschland
Tel: +49 - 681 / 99687-0
Fax: +49 - 681 / 99687-99
Mail: i...@meta-level.de
Web: www.meta-level.de

Rechtsform: Aktiengesellschaft
Sitz: Saarbrücken
HR B Nr. 13 380 Amtsgericht Saarbrücken
USt-IdNr. DE 1 38 17
Vorstände: Dipl.-Inform. Peter Badt und Dipl.-Inform. Peter Raber
Vorsitzender des Aufsichtsrats:  Reinhard Kuhn

--
You received this message because you are subscribed to the Google Groups "Jenkins 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/5fa5831a-e837-5b04-ca04-6be94f2b69e5%40meta-level.de.
For more options, visit https://groups.google.com/d/optout.

How to remove Blue Ocean from email links?

[Flominator]

Hi there,

since we started using Blue Ocean some of the notification emails on failed 
builds (at least the ones with "still failing" or "still unstable") contain 
URLs that lead to a Blue Ocean page. Since some of our users are using the 
console log parser plugin, they would prefer to see that one's result or at 
least the classic page with the link to it. Is there any way to configure 
this behavior without un-installing Blue Ocean?

We're using Jenkins v2.81 and BlueOcean v1.1.7

Thanks in advance,

Flo

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/d3eea7cb-fb65-4426-8d97-55bb887140ab%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

AW: In a shared library, what is the "vars/foo.txt" file USED for?

[Reinhold Fuereder]

Please note the PipelineSyntax/Global Variables Reference page is ONLY updated 
when the pipelines run is successful. And therefore ONLY for this pipeline (and 
not any others).

I think even if for "vars/file.groovy" there is no corresponding 
"vars/file.txt", then the PipelineSyntax/Global Variables Reference page shows 
an "empty" entry for global var "file".

HTH Reinhold

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/C3D41C0B1D5991438F1A43F586F4B47F73F8D7C2%40TIGER2010.xortex.local.
For more options, visit https://groups.google.com/d/optout.

Re: Mixing declarative and scripted pipeline syntax in one Jenkinsfile ...

[ishan jain]

Hi,

It is very much possible, as mentioned in the documentation. In fact it is 
very much required in my case.

On Wednesday, 4 October 2017 09:00:37 UTC+2, Eric Tan wrote:
>
> Hi,
>
> Is it possible to mix declarative and scripted pipeline syntax in one 
> Jenkinsfile ?
>
> For example, there is no withRun() equivalent in the declarative syntax.
>
> https://issues.jenkins-ci.org/browse/JENKINS-41581
>
> Thanks,
> Eric
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/990476d6-9cf2-4b49-a82d-95da59a90fe7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

RE: LDAP and systemctl jenkins restart

[Joaquin Henriquez]

Hi List

The issue was related to the directory /var/lib/jenkins/init.groovy.d

That contain a groovy script which I use it for the first time installation.

It seems it runs all the time Jenkins is restarted (even with a plugin 
installation restart)

Thk List.

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Michael Pailloncy
Sent: 04 October 2017 20:33
To: jenkinsci-users@googlegroups.com
Subject: EXTERNAL: Re: LDAP and systemctl jenkins restart

No, clearly it doesn't sound to be the way it should work :-)
Do you see any error/exception inside Jenkins's logs when you save your LDAP 
configuration or during Jenkins startup ?

Cheers

2017-10-03 15:55 GMT+02:00 Joaquin Henriquez 
>:
Hi ppl

I configure LDAP and everything is fine, but when I restart Jenkins “systemctl 
restart jenkins” the config for LDAP is removed.

Is this the way it should work or is there something wrong?

BR

Jo
--
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/745136b239784ed9913b334f55321187%40BSKEXCH2013HYPV.mwrinfosecurity.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAPO77c05gzcnneFjhofvKi7mpRee%3D%3DzfjQw_p3%3DA0LLmpi7row%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/58ac094653ff40cfbb9c8a3865707900%40BSKEXCH2013HYPV.mwrinfosecurity.com.
For more options, visit https://groups.google.com/d/optout.

Re: Bitbucket Branch Source Plugin & Endpoints

[Richard Bywater]

Thanks for the pointer - I'll see if I can fit in some time to whip
something up.

Richard.

On Thu, 5 Oct 2017 at 21:57 Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:

> If you want to take a stab at a PR, the relevant code you'd need to modify
> is:
>
>
> https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/master/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/BitbucketGitSCMBuilder.java#L176-L187
>
> and
>
>
> https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/master/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/BitbucketHgSCMBuilder.java#L170-L181
>
> You'll probably get a faster fix if you can provide a PR for the issue as
> my attention is assigned elsewhere at present
>
> On 5 October 2017 at 01:52, Richard Bywater  wrote:
>
>> Will do!
>>
>> Thanks
>> Richard.
>>
>> On Thu, 5 Oct 2017 at 21:20 Stephen Connolly <
>> stephen.alan.conno...@gmail.com> wrote:
>>
>>> Oversight. Please file a ticket in JIRA
>>>
>>> On 4 October 2017 at 20:46, Richard Bywater  wrote:
>>>
 Hi

 One of my colleagues is trying to get Jenkins 2 up and running with the
 Bitbucket Branch Source plugin using our Bitbucket Server infrastructure.

 We've run into an issue with the plugin as it appears it expects the
 server URL defined in the Bitbucket endpoint configuration to be the same
 as the one to be used for cloning purposes even for SSH.

 So for instance if you have defined
 https://bitbucketserver.example.com/bitbucket as the server URL, when
 cloning via SSH it attempts to use ssh://
 bitbucketserver.example.com:7999 (where 7999 is correctly read out of
 the clone link URLs returned by the Bitbucket API). In our case however,
 the web URL is different to the SSH url. For instance, based on the
 previous example, our SSH address is ssh://
 actualservername.example.com:7999/

 My question is that, rather than reusing the server URL for cloning
 operations, is there a reason why the clone URLs returned by the API for a
 repository aren't used instead? This would seem to allow Bitbucket to tell
 the plugin exactly where to look in case any other corner cases like this
 come up.

 Cheers
 Richard.

 --
 You received this message because you are subscribed to the Google
 Groups "Jenkins Users" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to jenkinsci-users+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/jenkinsci-users/CAMui945Sck2UTwhw8n7Ny0hbzc6CC_Aon8tDsXTBGa8cHzRFsw%40mail.gmail.com
 
 .
 For more options, visit https://groups.google.com/d/optout.

>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to jenkinsci-users+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMx3CsdxOe%3D1O53c%2B25HfVe%3DvJSRq6272%2BXz4RVryFpXRw%40mail.gmail.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-users+unsubscr...@googlegroups.com.
>>
> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/CAMui9440Rw18_vmatSgj_qA-72iRwxt_3BhQJgM4v3Wu7LTRDw%40mail.gmail.com
>> 
>> .
>
>
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMwN%3DdGZ8Udh3EYXX%2BncV7ventdzEL9jqaS2hrpHp0C7xA%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 

Re: Bitbucket Branch Source Plugin & Endpoints

[Stephen Connolly]

If you want to take a stab at a PR, the relevant code you'd need to modify
is:

https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/master/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/BitbucketGitSCMBuilder.java#L176-L187

and

https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/master/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/BitbucketHgSCMBuilder.java#L170-L181

You'll probably get a faster fix if you can provide a PR for the issue as
my attention is assigned elsewhere at present

On 5 October 2017 at 01:52, Richard Bywater  wrote:

> Will do!
>
> Thanks
> Richard.
>
> On Thu, 5 Oct 2017 at 21:20 Stephen Connolly  com> wrote:
>
>> Oversight. Please file a ticket in JIRA
>>
>> On 4 October 2017 at 20:46, Richard Bywater  wrote:
>>
>>> Hi
>>>
>>> One of my colleagues is trying to get Jenkins 2 up and running with the
>>> Bitbucket Branch Source plugin using our Bitbucket Server infrastructure.
>>>
>>> We've run into an issue with the plugin as it appears it expects the
>>> server URL defined in the Bitbucket endpoint configuration to be the same
>>> as the one to be used for cloning purposes even for SSH.
>>>
>>> So for instance if you have defined https://bitbucketserver.
>>> example.com/bitbucket as the server URL, when cloning via SSH it
>>> attempts to use ssh://bitbucketserver.example.com:7999 (where 7999 is
>>> correctly read out of the clone link URLs returned by the Bitbucket API).
>>> In our case however, the web URL is different to the SSH url. For instance,
>>> based on the previous example, our SSH address is ssh://
>>> actualservername.example.com:7999/
>>>
>>> My question is that, rather than reusing the server URL for cloning
>>> operations, is there a reason why the clone URLs returned by the API for a
>>> repository aren't used instead? This would seem to allow Bitbucket to tell
>>> the plugin exactly where to look in case any other corner cases like this
>>> come up.
>>>
>>> Cheers
>>> Richard.
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to jenkinsci-users+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/
>>> msgid/jenkinsci-users/CAMui945Sck2UTwhw8n7Ny0hbzc6CC
>>> _Aon8tDsXTBGa8cHzRFsw%40mail.gmail.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/
>> msgid/jenkinsci-users/CA%2BnPnMx3CsdxOe%3D1O53c%2B25HfVe%3DvJSRq6272%
>> 2BXz4RVryFpXRw%40mail.gmail.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-users/CAMui9440Rw18_vmatSgj_qA-72iRwxt_3BhQJgM4v3Wu7LTRDw%
> 40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMwN%3DdGZ8Udh3EYXX%2BncV7ventdzEL9jqaS2hrpHp0C7xA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Bitbucket Branch Source Plugin & Endpoints

[Richard Bywater]

Will do!

Thanks
Richard.

On Thu, 5 Oct 2017 at 21:20 Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:

> Oversight. Please file a ticket in JIRA
>
> On 4 October 2017 at 20:46, Richard Bywater  wrote:
>
>> Hi
>>
>> One of my colleagues is trying to get Jenkins 2 up and running with the
>> Bitbucket Branch Source plugin using our Bitbucket Server infrastructure.
>>
>> We've run into an issue with the plugin as it appears it expects the
>> server URL defined in the Bitbucket endpoint configuration to be the same
>> as the one to be used for cloning purposes even for SSH.
>>
>> So for instance if you have defined
>> https://bitbucketserver.example.com/bitbucket as the server URL, when
>> cloning via SSH it attempts to use ssh://bitbucketserver.example.com:7999
>> (where 7999 is correctly read out of the clone link URLs returned by the
>> Bitbucket API). In our case however, the web URL is different to the SSH
>> url. For instance, based on the previous example, our SSH address is ssh://
>> actualservername.example.com:7999/
>>
>> My question is that, rather than reusing the server URL for cloning
>> operations, is there a reason why the clone URLs returned by the API for a
>> repository aren't used instead? This would seem to allow Bitbucket to tell
>> the plugin exactly where to look in case any other corner cases like this
>> come up.
>>
>> Cheers
>> Richard.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/CAMui945Sck2UTwhw8n7Ny0hbzc6CC_Aon8tDsXTBGa8cHzRFsw%40mail.gmail.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMx3CsdxOe%3D1O53c%2B25HfVe%3DvJSRq6272%2BXz4RVryFpXRw%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAMui9440Rw18_vmatSgj_qA-72iRwxt_3BhQJgM4v3Wu7LTRDw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Why my tests in parallel don't finish the same way as sequential

[Ana MB]

Hi guys!

I'm running tests from my Jenkins and I've realized that if I run one only 
test, the result is SUCCESS; but if I run three tests in parallel, that 
test doesn't finish SUCCESS, it gets timeout.

My docker configuration is:

*version: "2"*


*services:*

*  selenium:*

*networks:*

*  mynet:*

*ipv4_address: 172.25.0.100*

*image: bufete/spider-selenium:beta1*

*ports:*

*  - "8080:8080"*

*  hub:*

*networks:*

*  mynet:*

*ipv4_address: 172.25.0.101*

*image: selenium/hub*

*ports:*

*  - "5001:"*

*environment:*

*  - GRID_BROWSER_TIMEOUT=1400*

*  - GRID_MAX_SESSION=10*

*  - GRID_TIMEOUT=120*

*  - GRID_NEW_SESSION_WAIT_TIMEOUT=-1*

*#  - GRID_TIMEOUT=900*

*  chrome:*

*image: selenium/node-chrome-debug:3.3.1*

*shm_size: 2g*

*links:*

*  - hub*

*volumes:*

*  - /dev/urandom:/dev/random*

*depends_on:*

*  - hub*

*environment:*

*  - HUB_PORT__TCP_ADDR=172.25.0.101*

*  - HUB_PORT__TCP_PORT=*

*  - NODE_MAX_SESSION=1*

*  - NODE_MAX_INSTANCES=1*

*  - SCREEN_WIDTH=1920*

*  - SCREEN_HEIGHT=1480*

*  - GRID_TIMEOUT=120*

*  - no_proxy=""*

*networks:*

*  - mynet*

*#ports:*

*#  - "666:5900"*

*volumes:*

*  - "/dev/shm:/dev/shm"*


Do you know how could I get the same result running my tests in parallel???

Thanks so much!!

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/48a32de9-e526-453a-bb2a-2eab7ce38101%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Bitbucket Branch Source Plugin & Endpoints

[Stephen Connolly]

Oversight. Please file a ticket in JIRA

On 4 October 2017 at 20:46, Richard Bywater  wrote:

> Hi
>
> One of my colleagues is trying to get Jenkins 2 up and running with the
> Bitbucket Branch Source plugin using our Bitbucket Server infrastructure.
>
> We've run into an issue with the plugin as it appears it expects the
> server URL defined in the Bitbucket endpoint configuration to be the same
> as the one to be used for cloning purposes even for SSH.
>
> So for instance if you have defined https://bitbucketserver.
> example.com/bitbucket as the server URL, when cloning via SSH it attempts
> to use ssh://bitbucketserver.example.com:7999 (where 7999 is correctly
> read out of the clone link URLs returned by the Bitbucket API). In our case
> however, the web URL is different to the SSH url. For instance, based on
> the previous example, our SSH address is ssh://actualservername.
> example.com:7999/
>
> My question is that, rather than reusing the server URL for cloning
> operations, is there a reason why the clone URLs returned by the API for a
> repository aren't used instead? This would seem to allow Bitbucket to tell
> the plugin exactly where to look in case any other corner cases like this
> come up.
>
> Cheers
> Richard.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-users/CAMui945Sck2UTwhw8n7Ny0hbzc6CC
> _Aon8tDsXTBGa8cHzRFsw%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMx3CsdxOe%3D1O53c%2B25HfVe%3DvJSRq6272%2BXz4RVryFpXRw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.