So if I understand this correctly, gitlab CI wants to be used something like this: - do a bunch of stuff in a 'job' with 'stages' - create artifacts on that job And then use those job artifacts as the release files? i.e. you're not meant to attach files to the release itself?

    artifacts:
        paths:
            - ds4
        expire_in: 1 week

    artifacts:
        paths:
            - ds4
        expire_in: 1 week

does this mean if someone wants to install a version of ds4 that's more than a week old, they're SOL?

Unknown User•4y ago

Message Not Public

Calego•4y ago

Oooooo, so I could file link to a job artifact

Unknown User•4y ago

Message Not Public

Calego•4y ago

interesting can you screenshot those buttons you have for me? what does that look like?

Unknown User•4y ago

Message Not Public

Calego•4y ago

ahhh neat So you're basically constantly building the build, and then release is the last step you trigger manually ?

Unknown User•4y ago

Message Not Public

Calego•4y ago

guessing you have this hosted somewhere where 'ci minutes' aren't a problem?

Unknown User•4y ago

Message Not Public

Calego•4y ago

the lint, the test, etc etc cleeeeverrrrr thanks @ghost

Leo The League Lion•4y ago

@calego gave LeaguePoints™ to @ghost (#5 • 252)

Unknown User•4y ago

Message Not Public

Calego•4y ago

Unknown User•4y ago

Message Not Public

Calego•4y ago

as is

Unknown User•4y ago

Message Not Public

Calego•4y ago

coming from Github's Actions, I feel like I've come from playskool's my first CI to being pushed off a cliff The docs are fantastic though It's interesting, I can see how this could end up being more powerful, it's just so much more painful to set up there's like 16 ways to achieve the same goal

Unknown User•4y ago

Message Not Public

Calego•4y ago

ok fair i havne't actually tried anything yet so they might be leading me into a false sense of knowing what i'm doing 😛

Unknown User•4y ago

Message Not Public

Calego•4y ago

Yeah but the 'actions' provide a nice layer of abstraction on a lot of things yeah

Unknown User•4y ago

Message Not Public

Calego•4y ago

as I browse these docs and look at all the examples I've found, I keep being like "oooh piece of candy" and I'm defiintely going to end up with a frankenstien's monster of a pipeline

Unknown User•4y ago

Message Not Public

Calego•4y ago

Alright, I thought I was being clever by separating my workflow into 3 jobs, but each one having to pull down a new docker container (which is the same for 2 of them) is a lot of time for what feels like very little benefit...

Unknown User•4y ago

Message Not Public

Calego•4y ago

not sure actually

Unknown User•4y ago

Message Not Public

Calego•4y ago

Calego•4y ago

so that's like 9-10 seconds at the start of each job... the job itself takes like 1 Oh more than that actually its like 40s seems like the recommendation is to .... not do that. lol I'm guessing these 'jobs' are most useful for codebases that can run many things in parallel and thus benefit from horizontal scaling like this in my case, one of my jobs is a simple "check these values and if they don't match, stop" I can easily tack that onto the other job, which would cut my time by a third...

Unknown User•4y ago

Message Not Public

Calego•4y ago

I've been sitting here like "haha look at all these fools with their single steps mixing concerns. I will transcend their obviously feeble understanding of the matrix and become neo!" narrator he did not

Unknown User•4y ago

Message Not Public

Calego•4y ago

yeah that's fair, I have mild concerns that since I'm running this on gitlab's dime, I need to conserve my "CI time"

Unknown User•4y ago

Message Not Public

Calego•4y ago

not sure, probably that feels a step too far down the rabbit hole right now though

Unknown User•4y ago

Message Not Public

Gaming

Programming

GitLab CI Pipelines