why my pipeline creates different workspaces?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

why my pipeline creates different workspaces?

jesus fernandez
I am quite new to Jenkins. I managed to create a simple pipeline to pull from perforce and build the project every commit, but I find sometimes it creates a different workspace such as project@2, project@tmp, project@tmp@2 and so on... why does this happen I have even set the customworkspace. Sorry if this is an obvious question. Here is my pipeline: 


pipeline 
{   
    agent {
        node {
            label 'master'
            customWorkspace 'C:/Users/User/.jenkins/workspace/Project'
        }
    }
    options { timestamps () }
    
    stages{
        stage('Get latest'){
            steps{
                p4sync charset: 'none', credential: 'somecredentials', 
                populate: syncOnly(force: false, have: true, modtime: false, 
                parallel: [enable: false, minbytes: '1024', minfiles: '1', threads: '4'], 
                pin: '', quiet: true, revert: false), 
                source: streamSource('//Project/main')   
            }
        }
        
        stage('Build'){
            steps{
                script {
                    def msbuild = tool name: 'MSBuild', type: 'hudson.plugins.msbuild.MsBuildInstallation'
                    bat "\"${msbuild}\" Project/Source/age2-GRDK.sln /t:Rebuild" 
                } 
            }
        }
    }
    
    post{
        changed{
            mail to: 'somemail',
            subject: "Status of: ${currentBuild.fullDisplayName}",
            body: "${env.JOB_NAME} has result ${currentBuild.result}"
        }
    }
   
}

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/2ceec923-1c83-4dc0-bb2e-839f66eccab6n%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: why my pipeline creates different workspaces?

Victor Martinez
Directories with an ampersand (like @tmp, @script, @libs, @2) are specifically created by the pipeline internals, each one got a different context. The ones with number are most likely related to a concurrent build running while other previous build is still running, to avoid clashing with accessing the same workspace

On Thursday, 8 October 2020 at 09:50:26 UTC+1 [hidden email] wrote:
I am quite new to Jenkins. I managed to create a simple pipeline to pull from perforce and build the project every commit, but I find sometimes it creates a different workspace such as project@2, project@tmp, project@tmp@2 and so on... why does this happen I have even set the customworkspace. Sorry if this is an obvious question. Here is my pipeline: 


pipeline 
{   
    agent {
        node {
            label 'master'
            customWorkspace 'C:/Users/User/.jenkins/workspace/Project'
        }
    }
    options { timestamps () }
    
    stages{
        stage('Get latest'){
            steps{
                p4sync charset: 'none', credential: 'somecredentials', 
                populate: syncOnly(force: false, have: true, modtime: false, 
                parallel: [enable: false, minbytes: '1024', minfiles: '1', threads: '4'], 
                pin: '', quiet: true, revert: false), 
                source: streamSource('//Project/main')   
            }
        }
        
        stage('Build'){
            steps{
                script {
                    def msbuild = tool name: 'MSBuild', type: 'hudson.plugins.msbuild.MsBuildInstallation'
                    bat "\"${msbuild}\" Project/Source/age2-GRDK.sln /t:Rebuild" 
                } 
            }
        }
    }
    
    post{
        changed{
            mail to: 'somemail',
            subject: "Status of: ${currentBuild.fullDisplayName}",
            body: "${env.JOB_NAME} has result ${currentBuild.result}"
        }
    }
   
}

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/8f7037b0-ca53-4a0d-9340-a36ccaa949bcn%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: why my pipeline creates different workspaces?

jesus fernandez

Gracias por aclararlo ahora tiene sentido :)
El viernes, 30 de octubre de 2020 a las 19:39:40 UTC+1, [hidden email] escribió:
Directories with an ampersand (like @tmp, @script, @libs, @2) are specifically created by the pipeline internals, each one got a different context. The ones with number are most likely related to a concurrent build running while other previous build is still running, to avoid clashing with accessing the same workspace

On Thursday, 8 October 2020 at 09:50:26 UTC+1 [hidden email] wrote:
I am quite new to Jenkins. I managed to create a simple pipeline to pull from perforce and build the project every commit, but I find sometimes it creates a different workspace such as project@2, project@tmp, project@tmp@2 and so on... why does this happen I have even set the customworkspace. Sorry if this is an obvious question. Here is my pipeline: 


pipeline 
{   
    agent {
        node {
            label 'master'
            customWorkspace 'C:/Users/User/.jenkins/workspace/Project'
        }
    }
    options { timestamps () }
    
    stages{
        stage('Get latest'){
            steps{
                p4sync charset: 'none', credential: 'somecredentials', 
                populate: syncOnly(force: false, have: true, modtime: false, 
                parallel: [enable: false, minbytes: '1024', minfiles: '1', threads: '4'], 
                pin: '', quiet: true, revert: false), 
                source: streamSource('//Project/main')   
            }
        }
        
        stage('Build'){
            steps{
                script {
                    def msbuild = tool name: 'MSBuild', type: 'hudson.plugins.msbuild.MsBuildInstallation'
                    bat "\"${msbuild}\" Project/Source/age2-GRDK.sln /t:Rebuild" 
                } 
            }
        }
    }
    
    post{
        changed{
            mail to: 'somemail',
            subject: "Status of: ${currentBuild.fullDisplayName}",
            body: "${env.JOB_NAME} has result ${currentBuild.result}"
        }
    }
   
}

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/5b498ef0-198c-4565-85e0-a0035608bdfcn%40googlegroups.com.