I've been scouring the internet for a way to do this and have had no success
We use git as our source control
Our jenkins server is running in windows
I am using windows batch scripts for several build tasks
I have written a batch script that checks the commit message for a specific
bit of text
Let me explain...
Very new in computing, don't know much about servers...
I recently started using Jenkins and have a master node running on my
working PC, and successfully configured a windows slave/agent on another PC.
Since we have other OS, I'm told to "deploy jenkins directly on our
>
> Thank you Tyler Croy;
I copied this directly from jenkins official doc, so very curious why they
forgot to put that final \ at the end of the line;
But still... I called a colleague and he added the \ at the end but we got
immediately another error... which I don't remember anymore.
I found, I need to put these commands in a script clause
thanks for you help!
On Wednesday, May 23, 2018 at 1:48:24 PM UTC-4, Edward Bond wrote:
> You can use that pattern, it’s arguably better than what I use.
>
> However my builds can look like, the environment really depicts how you
> can
It depends on what you want to do. I run my OSX slaves with the web start
and a login script. This allows my tests to interact with the window
manager. If you don't need that, then sticking with ssh is good. The only
downside I can see to the ssh setup is that you need to allow ssh on your
OSX
What did u tried?
On Thu, May 17, 2018 at 3:15 AM wrote:
> Hi All,
>
> Setting a new infrastructure please help me out how to setup jenkins with
> docker .? Individaly i know how to handle
>
>
> Thank you
> kirti
>
> --
> You received this message because you
is the assigned memory to the jenkins process big enough? You can monitor
the memory usage with https://wiki.jenkins.io/display/JENKINS/Monitoring if
it helps
Cheers
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this
Can you elaborate it a bit more? Is that something you see in the build
output or jenkins itself? Can you reproduce it locally using the same
environment/setup as you do within Jenkins? Can you also explain what
research have you done already? The whole stacktrace might help to know
further.
There are a few references in the suggested reference I posted earlier:
- https://jenkins.io/doc/book/installing/#docker
Your question is quite generic and you might need to be more specific,
otherwise it might be hard to help you with.
--
You received this message because you are subscribed
Although this is not a question about using jenkins itself but how to use
ansible and more specifically using the docker_container task. It smells
like the command parameter is overriding the default behaviour of the
jenkins image...
My two cents
--
You received this message because you are
You can use that pattern, it’s arguably better than what I use.
However my builds can look like, the environment really depicts how you can
execute things. I have a node labelled “default"
def runAndReturn(script){
toReturn = sh(script:script, returnStdout: true)
toReturn =
OK,
because I'm a beginner, wich pattern are you using?
On Wednesday, May 23, 2018 at 1:27:28 PM UTC-4, Edward Bond wrote:
> JB,
>
> Sorry, you are using the declarative syntax. I run my builds with a
> different pattern.
>
> Something like this might work for you,
>
>
>
> def
JB,
Sorry, you are using the declarative syntax. I run my builds with a
different pattern.
Something like this might work for you,
def runAndReturn(script){
toReturn = sh(script:script, returnStdout: true)
toReturn = toReturn[0..-2]
println toReturn
toReturn
Hello Edward,
This is my script at all
I think I did a mistake...
pipeline {
agent any
stages {
stage('Build project') {
steps {
git credentialsId: '*', url: 'https://**'
sh 'dotnet build
Hello,
if like this..
stage('Build image') {
steps {
script {
def TAG = sh (returnStdout: true, script: "git describe
--candidate=1 --tags").trim()
env.TAG = sh (returnStdout: true, script: "echo ${tag}
| cut -d\'-\'
Like this?
stage('Build image') {
steps {
sh """TAG=$(git describe --candidate=1 --tags)
TAG=$(echo $TAG | cut -d\'-\' -f 1)
WEB_IMAGE_NAME=$ACR_LOGINSERVER/my-project-1499882073260/test:$TAG
sudo docker build
Another option would be to use triple quoted strings to run all the
commands within the same shell execution. You'd have to deal with the env
variables and possibly escaping $ as needed.
sh """TAG=\$(git describe...) | cut -d
WEB_IMAGE_NAME=${ACR_LOGINSERVER}/.../\$(TAG)
sudo docker"""
>
> "C:\Program Files (x86)\Jenkins\workspace\Trivium 2015\Trivium 2015.sln"
> (default target) (1) ->
> "C:\Program Files (x86)\Jenkins\workspace\Trivium
> 2015\Trivium.Common\Trivium.Common.csproj" (default target) (2) ->
> (CoreCompile target) ->
> Utils\Mail\Sender.cs(15,30): error
>
> stage('Build image') {
> steps {
> sh 'TAG=$(git describe --candidate=1 --tags)'
> sh 'TAG=$(echo $TAG | cut -d\'-\' -f 1)'
> sh 'WEB_IMAGE_NAME=' + env['ACR_LOGINSERVER'] +
> '/my-project-1499882073260/test:' + env['TAG']
We have updated our Jenkins to Jenkins version 2.89.4
Nowadays we have the problem that our jobs thta are triggered don't work
like they should.
Tbh - the "SCM - Build periodically" in Jenkins jobs works randomly.
The triggered builds doesn't build caused by this. So we had to start the
jobs
Hello All,
Anyone knows how to edit a variable from shell and recover the result
across each next shells.
I'm trying to get the git tag version and to push the value into an env
variable.
In next, I'd like to re use the value into the next cmd shell.
It doesn't work!
Anyone has an idea? I
21 matches
Mail list logo