Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Feb 20 05:53
    @ashwilliams1 banned @matrixbot
  • Oct 18 2019 03:30
    @bradrydzewski banned @vityafx
  • May 07 2019 20:55
    @bradrydzewski banned @izznogooood
Adam Basfop Cavendish
@adamcavendish
So it might support build create right in the recent future

@ashwilliams1 I've dug a bit deeper and figured out it has to do with DRONE_SERVER_HOST in my Dockerfile vs. as an --env variable with docker run. For some reason when I use:

RUN echo "${DRONE_SERVER_HOST}"
ARG DRONE_SERVER_HOST
ENV DRONE_SERVER_HOST=$DRONE_SERVER_HOST
RUN echo "${DRONE_SERVER_HOST}"

The variable doesn't change from localhost but all others do.

Emmm ... this is interesting too

Adam Basfop Cavendish
@adamcavendish

we just received a PR yesterday I believe, but it has not landed in mainline

Interestingly I cannot find any PR created yesterday on github...

Brad Rydzewski
@bradrydzewski
@adamcavendish drone/go-scm#61
it was merged into a third party dependency yesterday, but that dependency is not yet updated in Drone core
Adam Basfop Cavendish
@adamcavendish
Great ... hope that it can fix the gitea
dekryptic
@dekryptic
After looking further into it I've learned that ENV variables always override ARG variables of the same name. So writing ENV DRONE_SERVER_HOST=$DRONE_SERVER_HOST is equivalent to ENV DRONE_SERVER_HOST=localhost where $DRONE_SERVER_HOST is always taken from the ENV variable defined in the base image rather than the ARG variable irrespective of order. I can work around this by passing in a build argument of a different name and then overriding the environment variable with another ENV instruction like this:
ARG DRONE_SERVER_HOST_ARG
ENV DRONE_SERVER_HOST=$DRONE_SERVER_HOST_ARG
I was also wondering if there's a way to "unset" ENV variables to avoid having them override ARG variables of the same name, but it's currently not possible: moby/moby#3465.
kolaente
@kolaente
Hey there, it seems like my drone instance is not picking up gitea tag events
The pipeline is not executed and I got nothing in the drone logs (DRONE_DEBUG enabled) but I can see the webhook being correctly fired in gitea
I'm running latest Gitea, maybe that could be an issue
but I think that would mean the webhook does not fire or something like that
Tom Vasile
@TomVasile
Hey all! From time to time I find some of the crons we configured in drone (& we use autoscaler) to be stuck in a state as it transitions to another pipeline. Has anyone come across this behavior? The crons work fine 99% of the time, just randomly I'll find 1 sitting in this stuck phase transitioning between pipeline 1 and pipeline 2.
the builds are listed as running in the database
but the autoscaler lists them as pending
ashwilliams1
@ashwilliams1
@kolaente there was a gitea regression. This pull request broke the webhook go-gitea/gitea#11082
ashwilliams1
@ashwilliams1
@TomVasile usually when something is stuck it is the result of an instance being killed when the pipeline is running.

the builds are listed as running in the database
but the autoscaler lists them as pending

the autoscaler looks at stages and uses the /api/queue endpoint. A build has one or many stages. So if you are looking at the build table in the database, you actually want to look at its stages in the stage table for an apples to apples compare

Sergei Lavinov
@Stalder
Hi, in promote docs i found, that it's possible to pass arguments to promote build. Is there any way to extract these arguments in my .drone.yml?
Sergei Lavinov
@Stalder
Oh, excuse me. Some experiments & and i fond, that it's enough just to use variable named like the argument you pass. e.g. builds/29/promote?target=stage&test_param=123 and echo $${test_param}
kolaente
@kolaente
@ashwilliams1 Thanks for pointing me to that, I'll look on the gitea side of things then
Thago
@Thagoo
Hi,
How can I set secrets ,I followed the docs and set as ot says but it isn't working
Thomas Boerger
@tboerger
@Thagoo you could only get help if you tell us more details, like what have you done, what do you expect.
gevalter
@gevalter
wondering if there is a way of telling the downstream plugin how to label its drone build, we have a use case which a downstream project is called by different upstreams and we want to see in the downstream which upstream called it
image.png
gevalter
@gevalter
here is the downstream build page now, all builds has the same label
Nathan Cooke
@3choBoomer

@bradrydzewski I think the paragraph you quoted is clear, it's just not clear on how the interaction between pipeline triggers and step triggers.

I would suggest something like the following:

If both step triggers and build triggers are defined, the build triggers take precedence. For example: If a build trigger is defined for a pull requests only and a step trigger is defined for pull requests and pushes, the step will only run on pull requests.

Ivan
@iver
Hello everybody. I have two drone versions (0.8.5 and latest).
My drone configuration works fine before my last change (add volumes to share files among steps) but I don't know why the drone server returns Cannot unmarshal '' to type string into a string value.
Are there any linter that works with my drone.yml file? I think is not enought information about the error.
Thomas Boerger
@tboerger
The 0.8 to latest format has changed heavily, they aren't compatible
The drone cli should have a command to transform the legacy version to the current version
Ivan
@iver
Sure, but the error is the same and the version is not matter. If the error show me the line or some thing more specific description could be better.
Thomas Boerger
@tboerger
That's what the yaml library gives back. Without details I can't tell where the issue comes from. Maybe you could try the lint command from drone cli
Ivan
@iver
Thank you @tboerger ! I changed from pipelines to steps and everything was better. I think this kind of errors are so complicated to debug.
Brad Rydzewski
@bradrydzewski
@iver Drone uses the go-yaml library which means we have to work with the error messages that it returns
I agree that better error reporting would make it easier to debug, however, this requires upstream improvements to the go-yaml library.
vaibhav jain
@vaibhav-jain
Hi guys, I'm new to drone and looking for a way to set the DRONE_MEMORY_LIMIT could someone please help me out?
Brad Rydzewski
@bradrydzewski
@vaibhav-jain please provide more information about your setup. The answer to this question depends on how you installed Drone and which runners you are using
vaibhav jain
@vaibhav-jain
@bradrydzewski docker runner
Brad Rydzewski
@bradrydzewski
the memory limit is passed to the docker-runner container as an environment variable
docker run -e DRONE_MEMORY_LIMIT=500000000 [OPTION]... drone/drone-runner-docker (500mb) https://docs.drone.io/runner/docker/configuration/reference/drone-memory-limit/
vaibhav jain
@vaibhav-jain
How do I see the current limit ? is there any default value for that?
Brad Rydzewski
@bradrydzewski
if you do not set a limit, the default docker limit is used (which is unlimited)
vaibhav jain
@vaibhav-jain
ok thanks @bradrydzewski
Kirill K
@agrrh

Hey guys!

Is it possible to use multiple conversion extensions at once? E.g. I'd like to use those two extensions:

Currently both of them rely on single DRONE_YAML_ENDPOINT which I could not share between 'em.

Brad Rydzewski
@bradrydzewski
@agrrh you cannot use two configuration extensions at the same time. With that being said, you can use a configuration extension and a conversion extension.
meltwater/drone-convert-pathschanged is very similar to microadam/drone-config-changeset-conditional, but since it is a conversion plugin, it can be used alongside bitsbeats/drone-tree-config
3 replies
YangWenbin
@ywbjja
Cannot use docker layering in drone to save push time https://docs.docker.com/storage/storagedriver/
dineshsalunke
@dineshsalunke
Can i change the timeout value for the digital ocean runner
AmengSong
@AmengSong
giteaļ¼šERRO[0040] oauth: cannot exchange code: 9Rw6MQCLLqoLihiv6vFIp780YAnTjw0hA8ZIqkIsdCY=: unauthorized_client: client is not authorized
DEBU[0040] cannot authenticate user: unauthorized_client: client is not authorized