nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

it is possible to hide some artifacts from build results?

Vladimir Avdeev1

Hi. I am create this structure:

Job "Build solutuin" collect binaries for deployment archive and tests to artifacts.

Job "Business logic testing" and "Data access testing" download shared artifacts from "Build solution" job, and use it.

Job "Package and Utils" download artifacts from "Build solution" job for collect the archive according to certain rules. I don't want to prepare deployment archive before testing, it is logical.

Question: How can I use binaries from first stage in last stage, that the user not see them?

P.S. Maybe bamboo can create internal artifact, for jobs only, not for users? or bamboo may hide some artifacts?

P.P.S. Now last job download artifacts from first job, and create own artifacts (zip archive). And user after build see shared artifacts from first stage and from last stage. I would like to user see only needed artifacts.

Accepted answers

Vladimir Avdeev1

My opinion:

checkout
build (collect test binaries as artifacts)
deploy to QA/dev
test QA/dev
deploy to Staging/prod
test Staging/prod

But in this case I shoul have ability to automatically deploy app to server.

In real case I haven't this ability. (we use "jump" host for deploy package to ec2 machines which do not have the Internet connection directly)

All comments

Ron Chan2

Vladimr,

One option is to have the first stage copy the "artifacts" (don't save in bamboo) to another location (e.g. another location on build server, a secured location on shared drive or even check it into source control). This process and configuration would obviously be invisible to the user, and only the last stage would know where to retrieve artifacts.

Hope that helps!

Ron

Vladimir Avdeev1

Ron,

I think it's not a very good option, because problems with the local network can make red build. I also need to create a structure of folders and files in another location, any changes into - red build.

I thought about it, really.

I had 2 choices:

1. Make a dependent plan, which would collect artifacts and pack them in an archive.

2. Re-build the project in the last step of this plan, compress files in bin folder and create target artifacts.

P.S. Maybe I have the wrong structure of the plan?

Vladimir Avdeev1

My opinion:

checkout
build (collect test binaries as artifacts)
deploy to QA/dev
test QA/dev
deploy to Staging/prod
test Staging/prod

But in this case I shoul have ability to automatically deploy app to server.

In real case I haven't this ability. (we use "jump" host for deploy package to ec2 machines which do not have the Internet connection directly)

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

bamboo

bamboo-administration