Set up autodeployments to Heroku for tests

[mariobehling]

Testing the app is important. Please set up autodeployments on each PR to Heroku.

[nikhilrayaprolu]

@Orbiter @sudheesh001 @daminisatya I am trying to deploy this project on heroku but I get this error when run on heroku local web

I am following instructions at this page: https://devcenter.heroku.com/articles/deploying-gradle-apps-on-heroku

[sudheesh001]

This is because the jar file seems to not point correctly to the Main-Class that needs to be executed. In the gradle , during jar generation task, I think it'll fix itself by adding a jar task with the manifest attribute to it.

jar {
  manifest {
    attributes(
      'Class-Path': configurations.compile.collect { it.getName() }.join(' '),
      'Main-Class': 'net.yacy.grid.<className>'
    )
  }
}

[nikhilrayaprolu]

@sudheesh001 I will try adding this to build.gradle

[nikhilrayaprolu]

@sudheesh001 now I am facing this issue,

is there any way to know how to use gradle run on heroku? gradle run works perfectly but the problem is with executing java files ourselves. or can we know which commands does Gradle use to run the built jar files?

[nikhilrayaprolu]

@daminisatya later I tried making a fat jar as I read that we have to create fatjar to pack dependencies. following https://stackoverflow.com/questions/4871656/using-gradle-to-build-a-jar-with-dependencies but Now I am facing this issue Could not find or load main class net.yacy.grid.mcp.MCP

but as per the project net.yacy.grid.mcp.MCP is the main class and it exists at https://github.com/.../main/java/net/yacy/grid/mcp/MCP.java

[sudheesh001]

Class not found errors are happening because it looks like the corresponding class files aren't available in the jar files. The way to avoid that is by creating a fat jar which has all the dependencies. So you're on the right track.

Can you extract the jar file and see if it contains the MCP.class in it?

[nikhilrayaprolu]

it has the MCP.class file

[sudheesh001]

Interesting, @Orbiter any reason you see here as to why the jar isn't running.