Gitlab CI passing dependencies among jobs











up vote
1
down vote

favorite












I am new to GitLab CI. I have a project where I have a Gitlab project and I have jobs generate, detectchanges, compile. The requirement is generate job generates some go files from templates, detectchanges need to act on same codebase including all the changes that generate job generates (like tempCreateTest/myfile.txt in example below) and compile again acts on same codebase and chanfes as genetate job acts upon. My problems are:
1. I couldnt see the changes that generate job generates even using dependencies. For example tempCreateTest/myfile.txt is not being seen by detect_changes and compile jobs
2. When I use dependency where exactly gitlab downloads the artifacts?



Can someone please answer this?



Here is my sample .gitlab-ci.yml



image: golang:1.11

stages:
- generate
- detect_changes
- build

before_script:
# Setup environment
- export GOPATH=/builds/$CI_PROJECT_NAMESPACE/$CI_PROJECT_NAME/go
- export GO_PROJECT_PATH=$GOPATH/src/gitlab.com/$CI_PROJECT_NAMESPACE/$CI_PROJECT_NAME
- export RAW_REPO_PATH=/builds/$CI_PROJECT_NAMESPACE/$CI_PROJECT_NAME/.
- mkdir -p $GO_PROJECT_PATH
- cp -r $RAW_REPO_PATH/. $GO_PROJECT_PATH
- cd $GOPATH
- export GO111MODULE=on
- cd $GO_PROJECT_PATH
- source ci.sh # This has functions that jobs use

generate_ci:
stage: generate
script:
- generate_ci_script
- mkdir tempCreateTest/ .
- echo "Some text here." > tempCreateTest/myfile.txt # Stages after generate should see the changes
artifacts:
untracked: true

detect_changes_ci:
stage: detect_changes
script:
- detect_changes_ci_script
dependencies:
- generate_ci

compile_ci:
stage: detect_changes
script:
- compile_ci_script
dependencies:
- generate_ci









share|improve this question


























    up vote
    1
    down vote

    favorite












    I am new to GitLab CI. I have a project where I have a Gitlab project and I have jobs generate, detectchanges, compile. The requirement is generate job generates some go files from templates, detectchanges need to act on same codebase including all the changes that generate job generates (like tempCreateTest/myfile.txt in example below) and compile again acts on same codebase and chanfes as genetate job acts upon. My problems are:
    1. I couldnt see the changes that generate job generates even using dependencies. For example tempCreateTest/myfile.txt is not being seen by detect_changes and compile jobs
    2. When I use dependency where exactly gitlab downloads the artifacts?



    Can someone please answer this?



    Here is my sample .gitlab-ci.yml



    image: golang:1.11

    stages:
    - generate
    - detect_changes
    - build

    before_script:
    # Setup environment
    - export GOPATH=/builds/$CI_PROJECT_NAMESPACE/$CI_PROJECT_NAME/go
    - export GO_PROJECT_PATH=$GOPATH/src/gitlab.com/$CI_PROJECT_NAMESPACE/$CI_PROJECT_NAME
    - export RAW_REPO_PATH=/builds/$CI_PROJECT_NAMESPACE/$CI_PROJECT_NAME/.
    - mkdir -p $GO_PROJECT_PATH
    - cp -r $RAW_REPO_PATH/. $GO_PROJECT_PATH
    - cd $GOPATH
    - export GO111MODULE=on
    - cd $GO_PROJECT_PATH
    - source ci.sh # This has functions that jobs use

    generate_ci:
    stage: generate
    script:
    - generate_ci_script
    - mkdir tempCreateTest/ .
    - echo "Some text here." > tempCreateTest/myfile.txt # Stages after generate should see the changes
    artifacts:
    untracked: true

    detect_changes_ci:
    stage: detect_changes
    script:
    - detect_changes_ci_script
    dependencies:
    - generate_ci

    compile_ci:
    stage: detect_changes
    script:
    - compile_ci_script
    dependencies:
    - generate_ci









    share|improve this question
























      up vote
      1
      down vote

      favorite









      up vote
      1
      down vote

      favorite











      I am new to GitLab CI. I have a project where I have a Gitlab project and I have jobs generate, detectchanges, compile. The requirement is generate job generates some go files from templates, detectchanges need to act on same codebase including all the changes that generate job generates (like tempCreateTest/myfile.txt in example below) and compile again acts on same codebase and chanfes as genetate job acts upon. My problems are:
      1. I couldnt see the changes that generate job generates even using dependencies. For example tempCreateTest/myfile.txt is not being seen by detect_changes and compile jobs
      2. When I use dependency where exactly gitlab downloads the artifacts?



      Can someone please answer this?



      Here is my sample .gitlab-ci.yml



      image: golang:1.11

      stages:
      - generate
      - detect_changes
      - build

      before_script:
      # Setup environment
      - export GOPATH=/builds/$CI_PROJECT_NAMESPACE/$CI_PROJECT_NAME/go
      - export GO_PROJECT_PATH=$GOPATH/src/gitlab.com/$CI_PROJECT_NAMESPACE/$CI_PROJECT_NAME
      - export RAW_REPO_PATH=/builds/$CI_PROJECT_NAMESPACE/$CI_PROJECT_NAME/.
      - mkdir -p $GO_PROJECT_PATH
      - cp -r $RAW_REPO_PATH/. $GO_PROJECT_PATH
      - cd $GOPATH
      - export GO111MODULE=on
      - cd $GO_PROJECT_PATH
      - source ci.sh # This has functions that jobs use

      generate_ci:
      stage: generate
      script:
      - generate_ci_script
      - mkdir tempCreateTest/ .
      - echo "Some text here." > tempCreateTest/myfile.txt # Stages after generate should see the changes
      artifacts:
      untracked: true

      detect_changes_ci:
      stage: detect_changes
      script:
      - detect_changes_ci_script
      dependencies:
      - generate_ci

      compile_ci:
      stage: detect_changes
      script:
      - compile_ci_script
      dependencies:
      - generate_ci









      share|improve this question













      I am new to GitLab CI. I have a project where I have a Gitlab project and I have jobs generate, detectchanges, compile. The requirement is generate job generates some go files from templates, detectchanges need to act on same codebase including all the changes that generate job generates (like tempCreateTest/myfile.txt in example below) and compile again acts on same codebase and chanfes as genetate job acts upon. My problems are:
      1. I couldnt see the changes that generate job generates even using dependencies. For example tempCreateTest/myfile.txt is not being seen by detect_changes and compile jobs
      2. When I use dependency where exactly gitlab downloads the artifacts?



      Can someone please answer this?



      Here is my sample .gitlab-ci.yml



      image: golang:1.11

      stages:
      - generate
      - detect_changes
      - build

      before_script:
      # Setup environment
      - export GOPATH=/builds/$CI_PROJECT_NAMESPACE/$CI_PROJECT_NAME/go
      - export GO_PROJECT_PATH=$GOPATH/src/gitlab.com/$CI_PROJECT_NAMESPACE/$CI_PROJECT_NAME
      - export RAW_REPO_PATH=/builds/$CI_PROJECT_NAMESPACE/$CI_PROJECT_NAME/.
      - mkdir -p $GO_PROJECT_PATH
      - cp -r $RAW_REPO_PATH/. $GO_PROJECT_PATH
      - cd $GOPATH
      - export GO111MODULE=on
      - cd $GO_PROJECT_PATH
      - source ci.sh # This has functions that jobs use

      generate_ci:
      stage: generate
      script:
      - generate_ci_script
      - mkdir tempCreateTest/ .
      - echo "Some text here." > tempCreateTest/myfile.txt # Stages after generate should see the changes
      artifacts:
      untracked: true

      detect_changes_ci:
      stage: detect_changes
      script:
      - detect_changes_ci_script
      dependencies:
      - generate_ci

      compile_ci:
      stage: detect_changes
      script:
      - compile_ci_script
      dependencies:
      - generate_ci






      gitlab gitlab-ci gitlab-ci-runner






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 9 hours ago









      Venu Chitta

      83210




      83210
























          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote













          You can use CI artifacts or caching to accomplish that. Please take a look at the examples from the previous links.






          share|improve this answer





















            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














             

            draft saved


            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53366764%2fgitlab-ci-passing-dependencies-among-jobs%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            0
            down vote













            You can use CI artifacts or caching to accomplish that. Please take a look at the examples from the previous links.






            share|improve this answer

























              up vote
              0
              down vote













              You can use CI artifacts or caching to accomplish that. Please take a look at the examples from the previous links.






              share|improve this answer























                up vote
                0
                down vote










                up vote
                0
                down vote









                You can use CI artifacts or caching to accomplish that. Please take a look at the examples from the previous links.






                share|improve this answer












                You can use CI artifacts or caching to accomplish that. Please take a look at the examples from the previous links.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered 1 hour ago









                djuarez

                694317




                694317






























                     

                    draft saved


                    draft discarded



















































                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53366764%2fgitlab-ci-passing-dependencies-among-jobs%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    404 Error Contact Form 7 ajax form submitting

                    How to know if a Active Directory user can login interactively

                    Refactoring coordinates for Minecraft Pi buildings written in Python