Caterina Curti Atlassian Team

Yes to this! See you on Friday (ok my Saturday @Bryan Guffey )!

Thank you @Bryan Guffey for posting and @Darryl Lee for adding the first comment! 💙 #ForgeLove P.S. @Darryl Lee did you mean a "Tour the Forge"? 😄

Thanks @josh- for pointing that out. This has been raised a few days ago as a suggestion to the Bitbucket team, here is the link: https://jira.atlassian.com/browse/BCLOUD-23558 I think you are already across this. Caterina

Hi @keyvan zare rami, the UUID behaviour for the REST APIs is described here: https://developer.atlassian.com/cloud/bitbucket/rest/intro/#uri-uuid You can also use the UUIDs for Git commands (e.g., cloning a repository), but I couldn't find documentation for that. Example git clone command where the first UUID is the…

@keyvan zare rami the UUID behaviour for the REST APIs is described here: https://developer.atlassian.com/cloud/bitbucket/rest/intro/#uri-uuid You can also use the UUIDs for Git commands (e.g., cloning a repository), but I couldn't find documentation for that. Example git clone command where the first UUID is the workspace…

Hi all, I've just published this article which shows how a user can access all PRs in a workspace across different projects and repositories: Access All Pull Requests in a Workspace The app doesn't have a project filter yet but that could be easily added. Let me know if that's something you would like to see and I'll…

Hi @Nagaraja (MicroGenesis TechSoft) . You could use the Forge app described in this article: * Access and Share Repository Size Data Across All Projects For your use case, the app also adds the size information in the repository overview for each user to see. It looks like this: The app also adds a Workspace Settings Menu…

The Forge app described in the Access and Share Repository Size Data Across All Projects article adds a Workspace Settings Menu page with the size of all repositories in a workspace and a download option to export the information in a CSV file. The app also adds the size information in the repository overview for each user…

If you are using Bitbucket Cloud, you can use the Forge app described in this article: - Access and Share Repository Size Data Across All Projects The app adds a Workspace Settings Menu page with the size of all repositories in a workspace and a download option to export the information in a CSV file. The app also adds the…

 Here you are @Georg Duemlein: https://jira.atlassian.com/browse/BCLOUD-23463

Hi @Georg Duemlein, At this stage, Project Level Dynamic Pipelines is not something that the team is working on. Hope this helps with defining how to set them up in your workspace. Edit: this is now tracked in this request https://jira.atlassian.com/browse/BCLOUD-23463 Cheers, Caterina

Hi all, Here is an article and a video with a working example of how this can be achieved using Dynamic Pipelines and a Forge app. The example shows how to replace the variable in an image name, but it can also be used as-is to substitute pipe names. Hope this helps, Caterina

Hi all, Here is an article and a video with a working example of how this can be achieved using Dynamic Pipelines and a Forge app. The example shows how to replace the variable in an image name, but it can also be used as-is to substitute pipe names. Hope this helps, Caterina

Hi all, Here is an article and a video with a working example of how this can be achieved using Dynamic Pipelines and a Forge app. The example shows how to replace the variable in an image name, but it can also be used as-is to substitute pipe names. Hope this helps, Caterina

Hi, I've just published an article and a video showing how you can use a variable as the image name. This solution is based on Dynamic Pipelines and requires a Forge app. The article shows how to replace an "IMAGE_TAG" value (image: node:$IMAGE_TAG) but would work with no changes when the variable contains the full name of…

Hello, I've just published an article and a video showing how you can use a variable as the image name. This solution is based on Dynamic Pipelines and requires a Forge app. Hope this helps, Caterina

Hello, Regarding the variables support in the image name, here is an article and a video I published showing how you can use a variable as the image name. This solution is based on Dynamic Pipelines and requires a Forge app. The article shows how to replace an "IMAGE_TAG" value (image: node:$IMAGE_TAG) but would work with…

Hi all, You can find here an article and a video showing how you can use a variable as the image name. This solution is based on Dynamic Pipelines and requires a Forge app. The article shows how to replace an "IMAGE_TAG" value (image: node:$IMAGE_TAG) but can be used for any other variables in the image tag or even the…

Hi all, I've just published an article and a video showing how you can use a variable as the image name. This solution is based on Dynamic Pipelines and requires a Forge app. The article shows how to replace an "IMAGE_TAG" value (image: node:$IMAGE_TAG) but would work with no changes when the variable contains the full…

That's an interesting idea @Jeffrey Hsiung However, that's currently not possible. Maybe you could explain a bit more about the context of this request? Thinking about other options, you could control the deployment process with a CI/CD that could add label on your repo at deploy time? And use forge tunnel to debug against…

Hi @Jeffrey Hsiung, Welcome to our community here and thank you for raising this point. I've updated the index.js in our reference apps repository to support nested pipelines (like custom, pull-requests, branches and tags). Hope this helps and let us know how it goes. Cheers, Caterina

It's been great to meet you in Barcelona! Thanks heaps for the write-up and mention! We'll be in touch!

Hi @Nuwan Udara Is this still an issue? I didn't test this today but I believe it should be possible as long as the app development environment is installed. You can check that by running the `forge install list` command. If this is still an issue to see if anything stands out in the output? Cheers, Caterina

Hi @Veeresh Let me start by welcoming you to the community. To achieve this, you'll need to use Dynamic Pipelines which allow you to add a single step (or a few) to multiple pipelines. Here is an article explaining how to add a step, hopefully this will help you get started. Caterina

Oh I see! My bad for not fully understanding the request here. You are right that the variables are currently not available in either the request or the REST APIs. I went ahead and created this ticket for tracking this suggestion: https://jira.atlassian.com/browse/BCLOUD-23395 At this stage, there is no alternative that I…

Hi @Nuwan Udara, Where are the variables defined? If they are defined on the repository, you want to use the `/2.0/repositories/{workspace}/{repo_slug}/pipelines_config/variables` endpoint (see…

For the ones of you that are following the Bitbucket changelog, here is the announcement: https://developer.atlassian.com/changelog/#CHANGE-1856

And finally, here you are: https://jira.atlassian.com/browse/BCLOUD-23289 (Sorry it took this long but please know that I've discussed this when you posted it with the team) Caterina

Thanks for sharing , @Andrew McMorris. Dynamic Pipelines provide a lot of flexibility, and that's key to managing pipelines at scale for most customers. We realized that this wouldn't be possible with configuration options. It should be pretty easy to get started, I'm also available for a 1:1 session if you like to spend…

Hi @Hareesh Kanchala, Now that Dynamic Pipelines have been released, you can achieve a greater level of flexibility with the Bitbucket pipelines. Last week, I published this article explaining how to add a step dynamically to a repository. This approach offers a greater level of flexibility, considering that the app logic…