There was mention of using 'labels' in a previous video related to dynamic pipelines. Where is the code for this?
@AtlassianDeveloper
Ай бұрын
Hi @Luuuuuuuuuuuuuuuu, The code for that is not available yet for the 'labels' example. You can check out the other examples/reference apps we have here: bitbucket.org/atlassian/forge-bitbucket-dynamic-pipelines-reference-apps
@ChristoKiwi
4 ай бұрын
Hmm, Is there a way to keep existing pipelines, and "include" a dynamic pipeline step within that 'locally handled' pipeline? If we have to throw away existing pipelines and go full dynamic, the dynamic pipelines are going to be HUGE and unwieldy to work with. (Because no two repos will have the same exact pipeline).
@AtlassianDeveloper
4 ай бұрын
Hi @ChristoKiwi, yes, with Dynamic Pipelines you have the flexibility to add steps to each repository pipeline. The repository for the Dynamic Pipeline presented in the webinar (available here: bitbucket.org/atlassian/forge-bitbucket-dynamic-pipeline-add-a-step ) adds to a repo where this pipeline (bitbucket.org/atlassian/forge-bitbucket-dynamic-pipeline-add-a-step/src/main/test/bitbucket-pipelines.yml ) is configured the step defined in the addGitSecretScan function of the bitbucket.org/atlassian/forge-bitbucket-dynamic-pipeline-add-a-step/src/main/src/index.js file.
@ChristoKiwi
4 ай бұрын
@@AtlassianDeveloper Do we have to script this kind of stuff? I would have thought our bitbucket-pipelines.yml file could simply have a line that imports the dynamic pipeline and then refer to it in a step.
@ChristoKiwi
4 ай бұрын
@@AtlassianDeveloper Any chance we can import dynamic pipelines into standard pipeline bitbucket-pipelines.yml files and utilise them as a step without having to write JS loops and adding further logic to our repos? We have hundreds of repos and the idea of scripting JS loops into each one has us looking for alternatives
@AtlassianDeveloper
4 ай бұрын
@ChristoKiwi This feature allows for much more flexibility which would be almost impossible to achieve via a simple reference in a step. It is also prone to errors as the repository admin of the "target repo" might not add the line to import the dynamic pipeline and this would lead to steps being missed. Developing an app to add a step is straightforward and should only take a few hours? Do you want to give it a try and let us know how it went? We also have a community here that is actively monitored for questions and feedback: community.atlassian.com/t5/Bitbucket-Cloud-x-Forge-EAP/gh-p/bitbucket-cloud-forge .
@AtlassianDeveloper
4 ай бұрын
@ChristoKiwi To clarify, if every repository requires a certain step, the app only needs to be installed at the workspace level. There is no need to add the logic to each repository and the app will only be one and each repository would use it.
Пікірлер: 9