Hi, I have a problem triggering the build of another repository via downstream plugin. My drone file looks like this:
kind: pipeline name: default steps: - name: build image: maven:3-openjdk-8 commands: - echo "hello world" - name: trigger image: plugins/downstream settings: server: http://drone.test.local token: from_secret: token fork: true repositories: - cicd/feat2@feature trigger: branch: - feature
When the trigger step runs I get "time="2020-05-29T21:03:16Z" level=fatal msg="Error: unable to trigger build for cicd/feat2@feature.\n"
Why does it keep failing?
sources.listto be an error. If anyone happens to know a way to make
apt-get updatefail on error, please tell me.
How should write pipeline where in single step , I want to run some commands on weekly schedule (download jar) and other commands ( execute agents) run on every event (without any schedule)?
Please share your inputs or any similar example for reference.
@bradrydzewski Can you please suggest ?
Hi, I am using the downstream plugin to trigger builds of feature branches in several repositories at push events.
Some of these repositories almost have the same drone file only referencing other repositories, just like this:
kind: pipeline name: default steps: - name: build image: maven:3-openjdk-8 commands: - echo "building something..." - name: trigger image: plugins/downstream settings: server: http://drone.domain.url token: from_secret: token fork: true repositories: - cicd/repo2@feature trigger: branch: - feature event: - push
The drone file in other repositories is the same except the line with the repository reference, which refers to the repository that was initially triggered.
The problem is that the repositories trigger each other even though the ones triggered by the downstream plugin were not pushed explicitly.
Is there a way to specify a trigger recognizing the potentially recursive nature of this situation?