I have Jenkins installed on a Linux server. It can run builds on itself. I
want to create either a Freestyle Project or an External Job that transfers
a bash script and runs it on two separate linux servers. Where in the GUI
do I configure the destination server when I create a build? I have add
+1
Default no-plugin install looks beautiful. Soon as you add any plugin that
adds an Action, it doesn't look so good anymore (mixed icons).
On Fri, Jan 29, 2016 at 10:30 PM, James Dumay wrote:
> Hi Afonso,
>
> Super impressed with your work here! Google have done an excellent job
> with their
Hi Afonso,
Super impressed with your work here! Google have done an excellent job with
their Material Design Language – works well in a lot of situations.
Did you have to do any changes that could break plugin compatibility along
the way? I know when various people have looked at this sort of w
I want to trigger a downstream project using a build of an upstream project
via REST api. Is this possible using the /build api ?
Thanks
Ramnath
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receivin
My question is the same as this discussion
https://groups.google.com/d/topic/jenkinsci-users/wbggN5aBHgU/discussion
Hope this helps
Thanks
Ramnath
On Friday, January 29, 2016 at 2:27:53 PM UTC-8, Ramnath Ananth wrote:
>
> Hi Jason.
>
> I have used the mentioned build with parameters option and i
Things looks much better with the flow below:
stage name: 'sync'
node("master") {
echo "before sync"
sh "sleep 10"
echo "after sync"
sh "date"
}
node("master") {
stage name: 'build', concurrency: 1
echo "before build"
sh "date"
sh "sleep 10"
echo "build 1/3"
sh "sleep 10"
Hi Jason.
I have used the mentioned build with parameters option and it works through
REST api. But the build result is not getting reflected in the Build
pipeline view. It is still in its original pipeline color and the builds
are not getting promoted further.
Thanks
Ramnath
On Friday, Jan
Maybe this will help:
https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Build
Look at 'Launching a build with parameters'
http://server/job/myjob/buildWithParameters?PARAMETER=Value
On Friday, January 29, 2016 at 10:36:43 AM UTC-8, Ramnath Ananth wrote:
>
> Hello,
>
> I am trying to t
If from the main page I click "Credentials" --> Global credentials
(unrestricted) --> I see a list of credentials. We'll call this List A.
If I click a Multibranch Pipeline job --> Click "Credentials" --> Global
credentials (unrestricted) --> I see a list of credentials I've added in
this specif
Hello,
I am trying to trigger a deploy job remotely using REST api and so far I
couldn't find any api which would know if the job is linked to the pipeline
or not.
I want to trigger a build job A. After successful completion of job A , I
want to trigger deploy job B. But there is no api to lin
*Please Excuse & advise, if this is not appropriate to continue post in an
old post. *
We are using the cloudbees jenkins. And are optimizing the workflows (the
new name: pipeline) to get some concurrency going. The way i understand
concurrency is the simultaneous execution. So a value of
con
There are 2 ways to make the resultant workspace path shorter. The path is made
up of the workspace root and your source code structure.
1. Change the “Workspace Root Directory” under System Configuration. My
windows master workspace resolves to: C:\Program Files
(x86)\Jenkins\jobs\JOBNA
Hi,
We currently are running Jenkins on a Windows Server box and a couple of
our projects are getting the "Path too long" error. I realize this is a
limitation of Windows but from looking around there are a couple options to
get around this in Jenkins.
The one we are trying is the short-works
Is there a way to clean the Build Executor Nodes? I have the ECS plugin
setup, but the Nodes don't get deleted, so I have over 1,000 nodes showing
offline which are never removed.
-Brandon Wagner
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
Look at the below entry:
- https://wiki.jenkins-ci.org/display/JENKINS/Starting+and+Accessing+Jenkins
Regarding the slave.jar
- https://issues.jenkins-ci.org/browse/JENKINS-16490
-
https://wiki.jenkins-ci.org/display/JENKINS/Distributed+builds#Distributedbuilds-WriteyourownscripttolaunchJenkinssla
The below wiki might help you out to debug your server
- https://wiki.jenkins-ci.org/display/JENKINS/Logging
And also the below plugin might show the version of each slave.jar file:
- https://wiki.jenkins-ci.org/display/JENKINS/VersionColumn+Plugin
Cheers
On Friday, 29 January 2016 13:24:24 UTC,
Here is the startup log
Jan 28, 2016 10:02:55 PM INFO org.eclipse.jetty.util.log.JavaUtilLog info
Started SelectChannelConnector@0.0.0.0:8080
Jan 28, 2016 10:02:55 PM INFO org.eclipse.jetty.util.log.JavaUtilLog info
Started Ajp13SocketConnector@0.0.0.0:8009
Jan 28, 2016 10:02:55 PM INFO org.
Thanks Mathus. We were able to resolve the issue by restarting the master.
Here’s what happened. A network outage caused the master to loose connectivity
to the slaves. After some time, the master issues a termination request to the
slaves. When the network issue was resolved, the slaves reconne
Does this actually run on a master? I ask as the documentation describes
how it's useful on slaves, but does NOT state that it is exclusively for
slaves...
On 29 January 2016 at 11:08, James Green wrote:
> My job wants to launch a Docker container. I've gone into System
> Configuration and asked
My job wants to launch a Docker container. I've gone into System
Configuration and asked it to install the latest Docker CLI from docker.io
When my job runs, it fails telling me it cannot find the 'docker' binary in
the path. There appears to be no attempt to install the tool automatically.
Surel
further experiments demonstrated my fix does not actually fix anything. I
need to look further at NodeProvisioner to understand why it behave so
badly when used in a Onte-time-executor docker container context.
2016-01-28 0:12 GMT+01:00 :
> Sure, that would be great.
> Thank you very much!
>
> --
(replies inline)
On Wed, 20 Jan 2016, Eero Arvonen wrote:
> Was there some sort of a christmas clean-up of older Jenkins-versions? I
> need to install an old version of Jenkins, 1.517 specifically, for red hat
> but everything older than 1.597 seems to have been removed even if it's
> listed r
(replies inline)
On Sat, 23 Jan 2016, Alex Domoradov wrote:
> I do really need exactly jenkins_1.565.2_all.deb (debian 7). Could anyone
> share with me?
archives.jenkins-ci.org is back up and running. It would appear that our
monitoring of this host was insufficient and that while Apache was r
I would like something
this https://wiki.jenkins-ci.org/display/JENKINS/Test+Results+Analyzer+Plugin
Le jeudi 28 janvier 2016 21:19:47 UTC+1, brian dawson a écrit :
>
> Hey RM.
>
> Can you clarify what you mean by "results of my build"? Success vs
> Failure? Test Results? Deployment events?
>
24 matches
Mail list logo