jitpack / jitci Goto Github PK

Hi,

It seems that I can't list my projects and organization anymore. I've tried to revoke the application access and log back in again, but that didn't work.

Looking at the websocket data, each requests receive as response:

{
    "_type": ".Status",
    "status": "error",
    "message": "401 - Unauthorized - "
}

Or even:

{
    "_type": ".Reply",
    "address": "GetOrgs5",
    "msg": {
        "_type": ".Err",
        "message": "{\"message\":\"Bad credentials\",\"documentation_url\":\"https://docs.github.com/rest\"}"
    },
    "_to": "GetOrgs5"
}

I think it's related to a token, but I can't find where I can add a valid one again.

I want to cancel my subscription to jitpack.io, but it is not displayed in my account! Support has not responded for many months! While the money is debited monthly! Email me asap!

Hello,
I think to reduce build time, dependencies in "init" could be saved somewhere else and are available in future builds, like with the github actions cache.

• Someone opened a PR on my project: diffplug/blowdryer#15
• JitCI completed successfully: https://jitci.com/gh/diffplug/blowdryer/74
• I merged, there were no other changes, so code is exactly the same post-merge
• JitCI reports failure on merge commit: https://jitci.com/gh/diffplug/blowdryer/75#
  • failure is on Build, but Test still succeeded
• Which is strange because the build log looks like it worked. In particular:

199.	BUILD SUCCESSFUL in 474ms
200.	9 actionable tasks: 2 executed, 7 up-to-date
201.	
202.	Uploading artifacts:
203.	 - dependency.info
204.	 - blowdryer-1.0.1.jar
205.	 - blowdryer-1.0.1-javadoc.jar
206.	 - tests.html
207.	 - blowdryer-1.0.1-sources.jar
208.	 - modules.info
Notification result: Emailed: [email protected]
Published to JitPack:
 - 
Published to JitPack:
 - 
JitPack. Updated status for com.diffplug/blowdryer/master-SNAPSHOT to Error. {"status":"ok"}
JitPack. Updated status for com.diffplug/blowdryer/master-SNAPSHOT to ok. {"status":"ok"}

So that you can have a code coverage indicator in your projects readme.
"Coverage: 100%"

The project is hosted on Github: https://github.com/hantsy/arquillian-container-glassfish-jakarta

When setup it on JitCI and publish to JitPack, there is a tag created on Github, and I try to trigger a build, it is built successfully.

In the Publish page, expand the Internal tab, it is versioned with 7.0.0, but in the JitPack tab, it used the commit id as version.

Why it can not use the tag directly.

I've just discovered and started using JitCI since I am already using JitPack to host my artifacts I thought I might as well use your CI service to have it all in one place.

The builds themselves seem to produce healthy artifacts and test are being executed correctly, however there is this quite concerning exception that keeps being thrown by every build:

        
ext.javassist.CannotCompileException: cannot find org.junit.platform.launcher.Launcher
	at ext.javassist.CtBehavior.insertAfter(CtBehavior.java:906)
	at ext.javassist.CtBehavior.insertAfter(CtBehavior.java:824)
	at jitci.agent.Instrumenter.instrumentCall(Instrumenter.kt:41)
	at jitci.agent.junit.JUnitTransformer.transform(JUnitTransformer.kt:35)
	at sun.instrument.TransformerManager.transform(TransformerManager.java:188)
	at sun.instrument.InstrumentationImpl.transform(InstrumentationImpl.java:428)
	at java.lang.ClassLoader.defineClass1(Native Method)
	at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
	at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
	at java.net.URLClassLoader.defineClass(URLClassLoader.java:468)
	at java.net.URLClassLoader.access$100(URLClassLoader.java:74)
	at java.net.URLClassLoader$1.run(URLClassLoader.java:369)
	at java.net.URLClassLoader$1.run(URLClassLoader.java:363)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.net.URLClassLoader.findClass(URLClassLoader.java:362)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
	at org.gradle.api.internal.tasks.testing.junitplatform.JUnitPlatformTestClassProcessor$CollectAllTestClassesExecutor.processAllTestClasses(JUnitPlatformTestClassProcessor.java:100)
	at org.gradle.api.internal.tasks.testing.junitplatform.JUnitPlatformTestClassProcessor$CollectAllTestClassesExecutor.access$000(JUnitPlatformTestClassProcessor.java:82)
	at org.gradle.api.internal.tasks.testing.junitplatform.JUnitPlatformTestClassProcessor.stop(JUnitPlatformTestClassProcessor.java:78)
	at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.stop(SuiteTestClassProcessor.java:61)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
	at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
	at org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
	at org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
	at com.sun.proxy.$Proxy2.stop(Unknown Source)
	at org.gradle.api.internal.tasks.testing.worker.TestWorker.stop(TestWorker.java:132)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
	at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
	at org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:175)
	at org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:157)
	at org.gradle.internal.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:404)
	at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
	at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)
	at java.lang.Thread.run(Thread.java:748)
Caused by: ext.javassist.NotFoundException: org.junit.platform.launcher.Launcher
	at ext.javassist.ClassPool.get(ClassPool.java:422)
	at ext.javassist.bytecode.Descriptor.toCtClass(Descriptor.java:571)
	at ext.javassist.bytecode.Descriptor.getReturnType(Descriptor.java:472)
	at ext.javassist.CtBehavior.getReturnType0(CtBehavior.java:331)
	at ext.javassist.CtBehavior.insertAfter(CtBehavior.java:858)
	... 45 more
        
  

I've did a bit of experimenting and found out that it's caused by adding this method to the test task:

`org.gradle.api.tasks.testing.useJUnitPlatform()`

Note that I've not tried configuring JUnit specific options, I only know that the exception is throws when no arguments are used. As I've said, for now everything works fine but I do think this matter should be looked into because it might cause problems down the road.

So that we can see tests running in real time

I selected Java 11

The log seems to indicate Java 12 was used.
https://jitci.com/gh/Q42/Q42Stats.Android/79
The build passed, tough.

Rather that having to manually select Java 11, I would hope jitci would detect the correct version from my code
https://github.com/Q42/Q42Stats.Android/tree/7372ff6aec1dacebff0130f858d8b28055ece106

There might be branches that you don't want to build on push (gh-pages).

When viewing large log files it can be useful to scroll back to the top of the screen

Hi! For some reason JitCI won't show any repo under my organization TheProgramSrc, even if they're open source:

If I press Find it will show up, but it would be nice to see it in the dropdown list :p

Support matrix builds to build project on different JDK versions and vendors.
Available docker images:
https://github.com/svenruppert/docker-image-generator

Gradle started requiring https connections for maven repositories; jitci uses http://cache without marking it as an allowed insecure repository.

The log states:

Using insecure protocols with repositories, without explicit opt-in, is unsupported. Switch Maven repository 'cache(http://cache)' to redirect to a secure protocol (like HTTPS) or allow insecure protocols. See https://docs.gradle.org/7.1/dsl/org.gradle.api.artifacts.repositories.UrlArtifactRepository.html#org.gradle.api.artifacts.repositories.UrlArtifactRepository:allowInsecureProtocol for more details.

Example: https://jitci.com/gh/minecraft-saar/minecraft-nlg/119

my project depends on node modules as a dependency. Without it, my project fails to compile.

I have manually pushed all the node modules in my repo and after that, I can get my project to build on Jitpack.

However, this approach is not sustainable.

How can I install node modules automatically on Jitpack rather than committing them to my repo

I can't log in. Also the build of my projects from GitHub is not working.
When I try to authorize through GitHub, I get error 524.
If it matters, I have two-factor authorization enabled on GitHub, but I don't think it should affect anything.

It would be great to see code coverage in JitCI since it already runs tests.

Ideally all types of code coverage should be supported:

• class
• method
• line

Most people expect code within GitHub repository,

not just README

Where are sources?

https://jitci.com/gh/publicLibs/RollingMavenHeader/builds/b1GYJ05N7GB30D01SHJ9A416DG/build.log

I need to provide the gpg key to build the artifact, to skip the signature I need to provide the argument below when building.
https://maven.apache.org/plugins/maven-gpg-plugin/sign-mojo.html

Skip doing the gpg signing.
Default value is: false.
User property is: gpg.skip.

mvn -B install -DskipTests -Dgpg.skip=true

So that you can add a badge to your readme saying "Dependencies: up to date"

I have added the JitCI badge and enabled unit tests, which are passing. The jitci badge color is grey and the label is None

What does this badge indicate? Coverage, tests passing?
Would be nice to clarify that in the docs

https://jitci.com/gh/Q42/Q42Stats.Android

So we can see Scala tests running in real-time

Hi, I have a github repository with a jitpack.yml file, which contains the following code:

install:
- FILE="-Dfile=myLibrary.aar"
- mvn install:install-file $FILE -DgroupId=myGroupId -DartifactId=myArtifactId -Dversion=5.1.4 -Dpackaging=aar -DpomFile=pom.xml

If I use Jitpack.io to publish the library, I can see it runs this install command and does it successfully in the logs. But when I try to setup JitCI, it runs mvn -B de.qaware.maven:go-offline-maven-plugin:resolve-dependencies.
My question is, how to setup JitCI, so that the jitapack.yml content would be executed?

At the moment, only master branch is recognized by jitci.
If that branch is main instead, jitci does not recognize it (grey badge, status none).
Could you build branch main if master does not exist (or vice versa) ?

Hello,

Service has been down for a long time.
Any news please ?
Do you plan to shutdown definitely ?

Thanks,
Nicolas.

Hello,
JitPack doesn't seem to be detecting the maven tests, even though they run successfully:

Is this normal? I couldn't find anything in settings about this.

At the moment artifacts are published to:

• internal JitCI repository
• JitPack.io

There should be a configuration option to publish to any Maven repository.

Note: it is already possible to publish to a repository using build tools but this would make it even easier.

I saw my email in the public logs:

https://jitpack.io/com/github/nbauma109/org-netbeans-modules-editor-settings-lib-storage/RELEASE126/build.log

Notification result: Emailed: ****@gmail.com

Please fix, emails are private.

I currently have 2 JitCi which are needed to make my build work.

I'd like to download those settings for backup / documentation purposes.

Alternatively, offer an option to read the settings from the github repo that is being built ie <repo root>/.jitci/settings.yml

Add ability to leave comments on a build.
This is useful when team members are discussing a build failure.

Support notification delivery to Discord via webhooks

Build and test is flaky, e.g.

• https://jitci.com/gh/diffplug/spotless-changelog/158#
• Could not GET 'http://cache/org/assertj/assertj-core/3.14.0/assertj-core-3.14.0.jar > Read timed out
• https://jitci.com/gh/diffplug/spotless-changelog/159#
• assemble task silently fails for no clear reason

Build and test are all rock solid locally, and rerunning CI fixes them. Big fan of JitPack, JitCI is super cool idea, but too flaky right now...

When I try to build my repo with jitci it says this error: https://hastebin.com/vagelimaco.py but i don't have any repo with the http protocol.

Whenever JitCI initializes we get this error

Cannot run program "exit" (in directory "/home/jitpack/build/<>"): error=2, No such file or directory

Here is the log

1. JitCI starting sdk-online-android build b1HH1NZEBSAGJC13TQ9YRF1FB5
2. Build #23 on branch ''. Commit: '6c393603'
3. Version: 1.0-17-gee5b1d9-303-20220904103105
5. 00:00 $ git config --global credential.helper cache
6. 00:00 $ git clone https://***@github.com/xxxxxxxxxxx/xxxxxxxxxxxxxxxxxxx .
7. Cloning into '.'...
8. 00:00 $ git checkout -qf 6c393603d1d2c81b4d6975c228c2f9b407aa987d
9. 00:00 $ git log --oneline -1
10. 6c39360 PDF with zoom feature commit for release version
11. 00:00 $ git show --name-status
12. commit 6c393603d1d2c81b4d6975c228c2f9b407aa987d
13. Author: xxxxxxxxxxxxxxxxxxxxxxxxxx
14. Date: Thu Dec 7 09:22:36 2023 +0100
    ...
    ...
    ...
15. 00:00 $ git branch -a --contains 1.0.0
16. • (HEAD detached at 6c39360)
17. master
18. remotes/origin/HEAD -> origin/master
19. remotes/origin/master
20. 00:01 $ git describe --always --long --tags
21. 1.0.0-0-g6c39360
22. Artifacts in DEPLOY_DIR: 0. Publish: true
23. 00:01 $ echo url not found
24. url not found
25. 00:01 $ exit 1
26. Cannot run program "exit" (in directory "/home/jitpack/build/<>"): error=2, No such file or directory
27. Command exit code: 1
28. Artifacts in DEPLOY_DIR: 0. Publish: true

We have replaced the repository information inside the Log

It seems to me that gradle builds can only fail at publish stage since the default command uses an unexisting init script outside of the project. The default command used is :

./gradlew deploy -I ../deploy.gradle

By activating --debug and --stacktrace in Settings -> Publish -> Run default commands, I could see that the file didn't exist

The specified initialization script '/home/jitpack/build/deploy.gradle' does not exist.

Hello,
JitPack seems to attempt to build the gh-pages branch, even when no pom.xml / build.gradle is present. Is there a way to disable the building on this branch? I hope that in the future it will automatically ignore builds on this branch.

If you have to deal with web apps, writing a web-component for example, you need selenium to test. This is easy with testcontainers. How to deal with DockerInDocker?

Although I chose JDK17 java and mvn will not change from Java 1.8, which causes the build to fail.
I also tried to install Java 17 through jabba, but then came across another issue — I've no clue how to install another maven. Tried to download from Apache CND server, but it also failed.

build.log
The project on JitCI

To notify about build results using PushOver:
https://pushover.net/api

If user has only authorized public repositories then JitCI won't be able to update commit status on GitHub.
There should be an indication in project settings that more permissions are required.

At the moment it is possible to grant more permissions using Add Repository (+) -> Private button.