Is it possible to use seriesci with a private organisation repo?

[arcticShadow]

Hi - I really like this concept and have been looking for something to track numerical data over time. In particular i'm looking at site speed and other performance results. Coupled with the GitHub status checks integration makes this quite an attractive product.

The first question - is will it work for a private Repo? I have the app installed ok, but the overview page loads forever.

Second question, is it possible to create the metrics on the fly?

I.E. The use case i am thinking of, is that we have multiple performance tests, and if a developer adds a new test, any configured integration here would not receive data until the metric had been created via the UI.

[zemirco]

Hey,

thank you for your feedback. I'm glad you like our product.

1. We're currently working on improving the branch view. See the latest tweet for a short summary https://twitter.com/seriesci/status/1203772487819022336. It's already working for series with just one line. Next we have to make it work for series with multiple lines. Then most of the features should work as expected and we will start working on integrating private repositories. So yes, private repos are high up on our priorities list.

2. I think you're talking about creating a new series on the fly? And that you're only able to create a new series by using the button + New series on our homepage? There is a new API that you can use to create a new series on the fly. It is a POST request to https://seriesci.com/api/repos/:owner/:repo/series and the JSON body must look like this

   {
     "name": "my-new-series",
     "description": "some more info about my new series"
   }

   If the series already exists you'll get 409 Conflict as a result. Does that help you? We might add more flexibility in the future where you can simply POST new values to some series and if the series does not exist we will create it for you.

I really like your use case. It helped a lot for understanding your problem.

[arcticShadow]

Thanks for your reply - regarding #2 I think I could make it work, with a post request to create new series. So that's not an issue.

However without being able tompost data for a private repo I can't utilise at the moment. I will be watching with keen interest.

If I might ask, is it a technical difference between private/public or is it working out the billing and payments for corporate use cases?

On Thu, 12 Dec 2019, 18:54 Mirco Zeiss, notifications@github.com wrote:

Hey,

thank you for your feedback. I'm glad you like our product.

1.

We're currently working on improving the branch view. See the latest tweet for a short summary https://twitter.com/seriesci/status/1203772487819022336. It's already working for series with just one line. Next we have to make it work for series with multiple lines. Then most of the features should work as expected and we will start working on integrating private repositories. So yes, private repos are high up on our priorities list. 2.

I think you're talking about creating a new series on the fly? And that you're only able to create a new series by using the button + New series on our homepage? There is a new API that you can use to create a new series on the fly. It is a POST request to https://seriesci.com/api/repos/:owner/:repo/series and the JSON body must look like this

{ "name": "my-new-series", "description": "some more info about my new series" }

If the series already exists you'll get 409 Conflict as a result. Does that help you? We might add more flexibility in the future where you can simply POST new values to some series and if the series does not exist we will create it for you.

I really like your use case. It helped a lot for understanding your problem.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/seriesci/support/issues/1?email_source=notifications&email_token=AAP4PTDMQKOKH4YXXAZXVB3QYHG2PA5CNFSM4JZXTVE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGVRS6Q#issuecomment-564861306, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAP4PTGB4UZCMVBPCWRFUW3QYHG2PANCNFSM4JZXTVEQ .

[zemirco]

I don't think there is a huge technical difference between public and private repos. The problem is more about security. At the moment everything at seriesci is public (except the /settings page for every repo). I have to make sure only the owner is able to see private repos and their metrics. Once I have this set up everything should work as expected.

As you said I also have to look into billing and payments but this is mostly done by GitHub directly. This is a huge advantage for me and for you. You don't have to create an extra account and you'll get only a single invoice. They charge 25% of the revenue but that's fine for what they provide. However they have certain requirements before I can create paid plans. https://developer.github.com/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/

As I said this is very high on my priority list. If you've got any other problems / ideas / wishes just let me know.

Kia ora

P.S. I studied in Christchurch in 2009/2010 for two semesters and it's always great to meet people from New Zealand.

[arcticShadow]

I studied in Christchurch in 2009/2010 for two semesters and it's always great to meet people from New Zealand.

That's awesome - NZ is a great place to live work and study ;-)

At the moment everything at seriesci is public I hadnt noticed that everything was public - Thats probably not ideal for my use case. I'll keep an eye on the evolution of your product!

[zemirco]

Hey,

good news 🎉Private repos are here 🍻🥳

They work exactly the same way public repos work. Install the GitHub App for your repository and start posting values to our API from your Continuous Integration. Of course you can test the workflow from your local machine. If you send values for the same hash more than once, the latest wins.

At the moment private repos are FREE! So check them out. Nothing special required to get started. No credit card and no extra plan.

Let me know if you've got any issues.

The best thing about private repos is that I can finally use seriesci.com to build seriesci.com. The whole application (database, cache, backend, communication, frontend) is a private monorepo here at GitHub. At the moment I'm tracking backend test coverage, Docker image size, frontend test coverage. I'm so looking forward to tracking even more values.

Enjoy!