nektos/act

Sven Assmann

@sassman

I wonder, if there was already someone finding or doing a web ui?

Cat™

@CatTheHacker

I'm not aware but that is absolutely worst idea

Sven Assmann

@sassman

How would you keep track of build logs etc? I mean if using act as a build pipeline runner..

Cat™

@CatTheHacker

I read them?

Not sure what you mean

thomascorthals

@thomascorthals

@sassman If you run the workflow on GitHub, you get a nice web UI with access to the build logs.

Cat™

@CatTheHacker

The goal of act is to make sure workflow works, once it works I just push it github and have GH Actions do stuff

from GH Actions you have separation per jobs, workflows, etc.

Sven Assmann

@sassman

Maybe my use case in mind is a bit different from yours. I'm talking about not using github for execution but an own ci - server. Like for example jenkins gives the UI and the runner infrastructure..

sure thing.. not suggesting that this is the act use case at all..

Cat™

@CatTheHacker

If you need to run stuff on demand there is https://agola.io/

Sven Assmann

@sassman

I read it but I think that is something different

Cat™

@CatTheHacker

that's a CI, like Jenkins

Sven Assmann

@sassman

a headless ci

Or am I missing something?

Cat™

@CatTheHacker

I'm quite confused on what are you trying to achieve

Sven Assmann

@sassman

Let me try it differently, let's say I have a github actions pipeline in my repo, but I do not use github, then that's pretty useless, right?

What I can do is use act to run it locally?

Cat™

@CatTheHacker

Technically yes

Sven Assmann

@sassman

cool, so imagine now a 3rd party self hostable thing, that acts as the CI server, get's notified by the repo (on push hook) and used act internally to execute the pipeline.

Cat™

@CatTheHacker

but why

Sven Assmann

@sassman

this thing I'm talking about would have some sort of UI (at least something that Github also shows - like build logs)

well there are a few good reasosn

Cat™

@CatTheHacker

there are so many better solutions already production-ready

Sven Assmann

@sassman

github actions are pretty well known to almost all meanwhile, no new DSL to learn not like Jenkinsfile or travis yml (the adoption rate is higher)

so this thing would have a market. Same as gitlab CI has or Bamboo or you name it

Cat™

@CatTheHacker

good luck trying to sell product that doesn't even work

Sven Assmann

@sassman

any solutions that support github actions pipelines?

AFAIK not..

Cat™

@CatTheHacker

azure pipelines have almost exact format as GH

cirrus-ci also have near exact format

Sven Assmann

@sassman

do they support those extensions from https://github.com/marketplace/actions

Cat™

@CatTheHacker

Sven Assmann

@sassman

see what I mean?

IMO this has an unbeatable lever

Cat™

@CatTheHacker

It's quite easy to beat though

Sven Assmann

@sassman

all those community actions are gold

Cat™

@CatTheHacker

as I said, good luck with broken product

Sven Assmann

@sassman

But anyways, I did not intend to debate. I only wanted to know what I found out .. thanks

photz

@photz

Hi, can any of you confirm if it's possible to access the outputs of a previous job through ${{needs...}}? Somehow I'm always getting [ReferenceError: 'needs' is not defined]

photz

@photz

just saw that there's an issue nektos/act#295

James Woolfenden

@JamesWoolfenden

newb question, im using act with the checkout action and it checks out the code from github to run the action. But i want the action to run with the code i have locally. Do i just put logic to skip the checkout step or can it default to this behaviour?

Cat™

@CatTheHacker

@JamesWoolfenden checkout should by default get your local code, can you provide workflow and full act command you used?

2 replies

Danny Staple

@dannystaple

Hello, do the -j flag and the --eventpath flag work together? It seems to not be setting github.ref.

Danny Staple

@dannystaple

Can I simulate a push with the overridden ref - in github.ref? Ie, on my branch, simulate a

'devel' branch push? Such that a check like if: contains(github.ref, 'devel') would be true?

sophie

@sophie07483506_twitter

Has anyone ever seen the following error when running act -n? I'm running it in a dockerfile.

"Please choose the default image you want to use with act:

- Large size image: +20GB Docker image, includes almost all tools used on GitHub Actions
- Medium size image: ~500MB, includes only necessary tools to bootstrap actions and aims to be compatible with all actions
- Micro size image: <200MB, contains only NodeJS required to bootstrap actions, doesn't work with all actions

Default image and other options can be changed manually in ~/.actrc"

I don't see any instructions to update the .actrc file with the default image, any guidance would be super appreciated on how to format that in the .actrc!

3 replies

Hannah Scovill

@hnsvill

My pipeline has docker build and push commands in it, and failed on docker build when I used the default medium-sized docker image, so I switched to act's larger docker runner option by deleting the .actrc file and chose large the next time I ran act. When I ran it again though, it hangs out here forever

[deploy lambda/build] 🧪  Matrix: map[python-version:3.8]
[deploy lambda/build] 🚀  Start image=nektos/act-environments-ubuntu:18.04

I've also tried messing with the default .actrc file by moving around the -P flags at the beginning of the lines but it didn't seem to made a difference. Any suggestions on what to try next? Thank you!

2 replies

Hannah Scovill

@hnsvill

I posted the solve to ^ in the thread, but a question I still have - related to Sophie's question above mine - how does the evaluation of the .actrc happen or work? If I can understand it more, I'm interested in possibly PR'ing a change that adds some titles/formatting/comments to the .actrc sort of like how an .aws/config file looks.

1 reply

Callum Sykes

@clicketyclackety

Where communities thrive

People

Repo info

Activity