Gitlab CI for multiple app folder in 1 Project RepoGitlabs artifact of one project used in further projectsPushing to GitLab repo does not trigger the Jenkins buildSetting up continues Integration on TFS with GitLab as RepoGitLab CI Pipeline on specific branch onlyImplementing a CI with gitlabHow to update repository with built project?Break Push in GitLab based on SonarQube Analysis ResultDocker build failed: tag invalid reference format (Gitlab CI)Gitlab CI: Is it possible to have sequential builds?

How can I implement regular expressions on an embedded device?

How to find better food in airports

How could a planet have one hemisphere way warmer than the other without the planet being tidally locked?

Why there are construction cranes on apparently completed buildings in New York?

Why is に used with this verb?

Tiny image scraper for xkcd.com

Life post thesis submission is terrifying - Help!

A magician's sleight of hand

Can doublestrike kill a creature with totem armor?

Left my gmail logged in when I was fired

What's the point of this macro?

Are language and thought the same?

Is it possible to observe space debris with Binoculars?

A Meal fit for a King

Round away from zero

Did the US Climate Reference Network Show No New Warming Since 2005 in the US?

What's the difference between a share and a stock?

Does blackhole merging breaks their event horizon seggregation?

Dissuading my girlfriend from a scam

Comparing elements in a nested list to generate a new list

Travel to USA with a stuffed puppet

Global variables and information security

'This one' as a pronoun

Never make public members virtual/abstract - really?



Gitlab CI for multiple app folder in 1 Project Repo


Gitlabs artifact of one project used in further projectsPushing to GitLab repo does not trigger the Jenkins buildSetting up continues Integration on TFS with GitLab as RepoGitLab CI Pipeline on specific branch onlyImplementing a CI with gitlabHow to update repository with built project?Break Push in GitLab based on SonarQube Analysis ResultDocker build failed: tag invalid reference format (Gitlab CI)Gitlab CI: Is it possible to have sequential builds?






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








0















We have following setup
1 Project repo with
–> App1 (source code)
–> App2 (source code)



Now we have single(1) .gitlab-ci.yml at repo level.



What we want to achieve is:



With each checkin/commit to Apps (App1 or App2) should trigger CI build and push its own artifacts to registry.



Can we execute Gitlab-CI[with the same .gitlab-ci.yml from root level] based upon commit/checkin specific Folder Name Apps (App1 or App2)(which has the commit changes ,to be build) ?



Is it possible?



Please guide.










share|improve this question


























  • what do you mean 'can we do parameterze'? do you want to trigger a different build step by the committed code?

    – Amityo
    Mar 28 at 17:33











  • Thanks Amityo , what I mean to say is that by parameterise is that same CI file getting fired upon commit into any of Apps (App1 or App2) in the single Repo Project

    – Jas Singh
    Mar 29 at 5:31


















0















We have following setup
1 Project repo with
–> App1 (source code)
–> App2 (source code)



Now we have single(1) .gitlab-ci.yml at repo level.



What we want to achieve is:



With each checkin/commit to Apps (App1 or App2) should trigger CI build and push its own artifacts to registry.



Can we execute Gitlab-CI[with the same .gitlab-ci.yml from root level] based upon commit/checkin specific Folder Name Apps (App1 or App2)(which has the commit changes ,to be build) ?



Is it possible?



Please guide.










share|improve this question


























  • what do you mean 'can we do parameterze'? do you want to trigger a different build step by the committed code?

    – Amityo
    Mar 28 at 17:33











  • Thanks Amityo , what I mean to say is that by parameterise is that same CI file getting fired upon commit into any of Apps (App1 or App2) in the single Repo Project

    – Jas Singh
    Mar 29 at 5:31














0












0








0








We have following setup
1 Project repo with
–> App1 (source code)
–> App2 (source code)



Now we have single(1) .gitlab-ci.yml at repo level.



What we want to achieve is:



With each checkin/commit to Apps (App1 or App2) should trigger CI build and push its own artifacts to registry.



Can we execute Gitlab-CI[with the same .gitlab-ci.yml from root level] based upon commit/checkin specific Folder Name Apps (App1 or App2)(which has the commit changes ,to be build) ?



Is it possible?



Please guide.










share|improve this question
















We have following setup
1 Project repo with
–> App1 (source code)
–> App2 (source code)



Now we have single(1) .gitlab-ci.yml at repo level.



What we want to achieve is:



With each checkin/commit to Apps (App1 or App2) should trigger CI build and push its own artifacts to registry.



Can we execute Gitlab-CI[with the same .gitlab-ci.yml from root level] based upon commit/checkin specific Folder Name Apps (App1 or App2)(which has the commit changes ,to be build) ?



Is it possible?



Please guide.







gitlab gitlab-ci






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Mar 29 at 7:55







Jas Singh

















asked Mar 28 at 3:43









Jas SinghJas Singh

11 bronze badge




11 bronze badge















  • what do you mean 'can we do parameterze'? do you want to trigger a different build step by the committed code?

    – Amityo
    Mar 28 at 17:33











  • Thanks Amityo , what I mean to say is that by parameterise is that same CI file getting fired upon commit into any of Apps (App1 or App2) in the single Repo Project

    – Jas Singh
    Mar 29 at 5:31


















  • what do you mean 'can we do parameterze'? do you want to trigger a different build step by the committed code?

    – Amityo
    Mar 28 at 17:33











  • Thanks Amityo , what I mean to say is that by parameterise is that same CI file getting fired upon commit into any of Apps (App1 or App2) in the single Repo Project

    – Jas Singh
    Mar 29 at 5:31

















what do you mean 'can we do parameterze'? do you want to trigger a different build step by the committed code?

– Amityo
Mar 28 at 17:33





what do you mean 'can we do parameterze'? do you want to trigger a different build step by the committed code?

– Amityo
Mar 28 at 17:33













Thanks Amityo , what I mean to say is that by parameterise is that same CI file getting fired upon commit into any of Apps (App1 or App2) in the single Repo Project

– Jas Singh
Mar 29 at 5:31






Thanks Amityo , what I mean to say is that by parameterise is that same CI file getting fired upon commit into any of Apps (App1 or App2) in the single Repo Project

– Jas Singh
Mar 29 at 5:31













1 Answer
1






active

oldest

votes


















0
















If you run a specific stage based on the changes in App1 or App2 you can use the only+ changes keywords:




Using the changes keyword with only or except, makes it possible to define if a job should be created based on files modified by a git push event.




Define two stages - one for App1, one for App2 and add the only + changes keyword:



build_App1:
script: ...
only:
changes:
- path/to/App1/**/*


see here for more details. And make sure to read the caveats here






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',
    autoActivateHeartbeat: false,
    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%2f55389839%2fgitlab-ci-for-multiple-app-folder-in-1-project-repo%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









    0
















    If you run a specific stage based on the changes in App1 or App2 you can use the only+ changes keywords:




    Using the changes keyword with only or except, makes it possible to define if a job should be created based on files modified by a git push event.




    Define two stages - one for App1, one for App2 and add the only + changes keyword:



    build_App1:
    script: ...
    only:
    changes:
    - path/to/App1/**/*


    see here for more details. And make sure to read the caveats here






    share|improve this answer





























      0
















      If you run a specific stage based on the changes in App1 or App2 you can use the only+ changes keywords:




      Using the changes keyword with only or except, makes it possible to define if a job should be created based on files modified by a git push event.




      Define two stages - one for App1, one for App2 and add the only + changes keyword:



      build_App1:
      script: ...
      only:
      changes:
      - path/to/App1/**/*


      see here for more details. And make sure to read the caveats here






      share|improve this answer



























        0














        0










        0









        If you run a specific stage based on the changes in App1 or App2 you can use the only+ changes keywords:




        Using the changes keyword with only or except, makes it possible to define if a job should be created based on files modified by a git push event.




        Define two stages - one for App1, one for App2 and add the only + changes keyword:



        build_App1:
        script: ...
        only:
        changes:
        - path/to/App1/**/*


        see here for more details. And make sure to read the caveats here






        share|improve this answer













        If you run a specific stage based on the changes in App1 or App2 you can use the only+ changes keywords:




        Using the changes keyword with only or except, makes it possible to define if a job should be created based on files modified by a git push event.




        Define two stages - one for App1, one for App2 and add the only + changes keyword:



        build_App1:
        script: ...
        only:
        changes:
        - path/to/App1/**/*


        see here for more details. And make sure to read the caveats here







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Mar 29 at 8:55









        AmityoAmityo

        1,93912 silver badges21 bronze badges




        1,93912 silver badges21 bronze badges





















            Got a question that you can’t ask on public Stack Overflow? Learn more about sharing private information with Stack Overflow for Teams.







            Got a question that you can’t ask on public Stack Overflow? Learn more about sharing private information with Stack Overflow for Teams.



















            draft saved

            draft discarded
















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid


            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.

            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55389839%2fgitlab-ci-for-multiple-app-folder-in-1-project-repo%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

            Kamusi Yaliyomo Aina za kamusi | Muundo wa kamusi | Faida za kamusi | Dhima ya picha katika kamusi | Marejeo | Tazama pia | Viungo vya nje | UrambazajiKuhusu kamusiGo-SwahiliWiki-KamusiKamusi ya Kiswahili na Kiingerezakuihariri na kuongeza habari

            SQL error code 1064 with creating Laravel foreign keysForeign key constraints: When to use ON UPDATE and ON DELETEDropping column with foreign key Laravel error: General error: 1025 Error on renameLaravel SQL Can't create tableLaravel Migration foreign key errorLaravel php artisan migrate:refresh giving a syntax errorSQLSTATE[42S01]: Base table or view already exists or Base table or view already exists: 1050 Tableerror in migrating laravel file to xampp serverSyntax error or access violation: 1064:syntax to use near 'unsigned not null, modelName varchar(191) not null, title varchar(191) not nLaravel cannot create new table field in mysqlLaravel 5.7:Last migration creates table but is not registered in the migration table

            은진 송씨 목차 역사 본관 분파 인물 조선 왕실과의 인척 관계 집성촌 항렬자 인구 같이 보기 각주 둘러보기 메뉴은진 송씨세종실록 149권, 지리지 충청도 공주목 은진현