Help needed to publish and run sbt from AWS

[pablopareja]

Hi!

It takes forever to publish the project with my internet connection so I wanted to do everything from AWS and simply commit-push the code from local. Could you please help me out with what I exactly would need to config for that? @eparejatobes @laughedelic Thanks!

:octopus:

[laughedelic]

first things that you need on the instance: java, sbt & git. I don't know, what else? just clone the repo and run sbt

[eparejatobes]

@laughedelic WDYT?

[eparejatobes]

but I guess it'd be nice to have a hook or something

[pablopareja]

isn't it something that you already do for other projects?

[eparejatobes]

we want to, but we're not doing it right now

[laughedelic]

@pablopareja publishing from ec2? not that I know. @eparejatobes what the heck hook?

[pablopareja]

aahm I thought that there was some sort of standarized way to do it that was already been used in other projects.

[laughedelic]

well, you can apply a git statika bundle. and get the starting configuration, then do what you want. or write a bundle for this particular task and just apply it.

[pablopareja]

ein whaat? :confused: :laughing:

[eparejatobes]

@laughedelic a github webhook

[eparejatobes]

there's even one for sns: https://api.github.com/hooks

[eparejatobes]

and for sqs :)

[laughedelic]

@eparejatobes I don't know anything about it...

@pablopareja a short answer to this issue: no we don't have a one-button solution for you.

[eparejatobes]

but we need one

[eparejatobes]

in general

[laughedelic]

agree. and also many other cool things...

[pablopareja]

well let me know if I can help with something, but I have to say that this would be extremely helpful for me! :smiley:

[eparejatobes]

Let me think about it a bit first, and I'll tell you tomorrow

[pablopareja]

OK!

[marina-manrique]

Maybe I'm saying nonsense but @evdokim gave me a good idea (I had a similar issue for running metapasta and nispero). He has an autoscalling group with everything he needs to publish and do whatever he wants and then he sets the capacity to 1 when he wants an instance for publishing and to 0 when he wants to terminate with it

Maybe it takes a bit to configure this for the first time but then it's useful for all the projects

[evdokim]

@marina-manrique it works perfect for adhoc personal usage. But in general it's quite easy to configure build server with:

• auto scaling group
• load balancer
• githook

[pablopareja]

@eparejatobes any updates on this?

[eparejatobes]

How this could be done in a simple way:

1. set up an autoscaling group with Jenkins instances together with a funny guy controlling its capacity (after x hours without builds kill everything etc)
2. an sbt plugin which would configure where this project is supposed to be built and how (basically adding a git hook)

We could easily extend this to importing data, by creating projects for each module; building/releasing them would be done in specific autoscaling groups with the right machine types etc.

[pablopareja]

ok, let's do this when we have some time for it :wink:

[eparejatobes]

Yes, I want to have this for 1.0